Related
Hi,
I need to do a factory reset (to see if it solves a problem that Asus could not solve) and in anyway I read it's safer to wipe data before sending to factory for repair.. So I'd like to make a full backup before this wipe and before the sending to repair..
I installed free Titanium backup (my tablet is rooted), but I'm confused on what I should do before doing the reset and the tutorials I found on Titanium even confused me more..(if you're aware of a nice tutoriel, link would be welcome, because I found none very explicit on xda and even on the web..)
-first, should I use the Asus tool for backup or Titanium ?
- Should I perform a full backup of apps only or apps+system ? I read that system restore could create issues in case restore is not done on same firmware, and I don't know with which FW my tablet will come back from repair.. so should I use apps+system anyway, or make 2 backups (apps first then system or vice versa ?) I'd prefer to restore my tablet as clsoe as it is today, even if possible with bluetooth pairs and wifi connections..
-Should I backup manually my personal files (videos ,various docs, pictures,..) before using Titanium ? (for instance to save space and make nbackups smaller?) If yes, how do we know which folders are backuped up by Titanium and which are not ?
- My sdcard is already largely used with only a few GB left. Can I ask Titanium to save directly to a PC ? Or should I use another sdcard (but then, what will happen to apps installed on sdcard ?) ?
Thanks a lot for your hints.
Ricorico94
There are several different options for you to choose from but I will share the way I usually back up my tablet. I flash different ROMs frequently and have had to use backups quite a bit.
I usually use Titanium Backup to backup everything but only restore non-system apps and data. You're right that restoring system data can result in problems if restoring to different ROMs, not necessarily firmware. It depends on how much the firmware has changed. Since there might be big enough changes that it might screw everything up then I'd avoid restoring system apps and data. If your tablet is backed up to Google, it will sometimes keep the WiFi and Bluetooth pairings and restore them once you log back into your Google account. Not always though. Also I'm not sure that the free version of Titanium Backup can save any place other than an SD card. The paid version can save to Dropbox and Google Drive.
If you're sending your tablet in for repair, you should move all of your personal files to your computer or SD card, deleting them off the tablet. At least, that's what I'd do.
There is one more option which would make saving a lot easier and that is if you have a custom recovery installed like TWRP or CWM you can create a Nandroid Backup of everything, System, Data and all. With all your pictures, etc the file would be huge but you could move that to your computer and restore it when your tablet comes back. That would keep an exact copy of your system and replace whatever ASUS does to it with what you currently have. If I wanted to keep my tablet as close to how I set it up, this is what I would do. Of course, your tablet has to be rooted and unlocked to do so.
wrynn7 said:
There are several different options for you to choose from but I will share the way I usually back up my tablet. I flash different ROMs frequently and have had to use backups quite a bit.
I usually use Titanium Backup to backup everything but only restore non-system apps and data. You're right that restoring system data can result in problems if restoring to different ROMs, not necessarily firmware. It depends on how much the firmware has changed. Since there might be big enough changes that it might screw everything up then I'd avoid restoring system apps and data. If your tablet is backed up to Google, it will sometimes keep the WiFi and Bluetooth pairings and restore them once you log back into your Google account. Not always though. Also I'm not sure that the free version of Titanium Backup can save any place other than an SD card. The paid version can save to Dropbox and Google Drive.
If you're sending your tablet in for repair, you should move all of your personal files to your computer or SD card, deleting them off the tablet. At least, that's what I'd do.
There is one more option which would make saving a lot easier and that is if you have a custom recovery installed like TWRP or CWM you can create a Nandroid Backup of everything, System, Data and all. With all your pictures, etc the file would be huge but you could move that to your computer and restore it when your tablet comes back. That would keep an exact copy of your system and replace whatever ASUS does to it with what you currently have. If I wanted to keep my tablet as close to how I set it up, this is what I would do. Of course, your tablet has to be rooted and unlocked to do so.
Click to expand...
Click to collapse
Hi,
Thanks a lot for this advice. Do you know if I can still make 2 separate backups, so that I could use system backup if there's no FW change ?
Regarding the TWRP custom recovery, I understood that since I am already with FW 10.4.4.25 (android 4.1.1) and only rooted, there's no way to install customer recovery. Did I understood properly, or is there a way to downgrade to previous versions first, istall custom and upgrade again back to current FW ?
What do you mean by "tablet backed up to Google" ? I have "save my datas" checked under "backup" menu of parameters, but is there a way to check that there's indeed something in their servers already ?
br,
Ricorico94
You could make as many backups as you wanted. Titanium Backup allows you to restore whatever you want it to so you really only have to make one backup. You can restore everything but the system apps and data or everything. You can even use it to uninstall or freeze what you're not using (as long as it's not an integral part of the FW of course). It's not an all or nothing deal. I would still move all of your personal data to a computer or SD card so nothing happens to it.
My understanding is that installing CWM or TWRP require your device to be unlocked using an app that is provided through the ASUS website. Just being rooted isn't sufficient. If you don't want to unlock your device then you're stuck with using the Titanium Backup method. Just make sure it is saving your apps to an external SD card and not the internal one.
And yes, I was referring to the setting that you already have checked about Google backing up your data. It doesn't always restore everything though so you might have to pair everything again anyway.
ricorico94 said:
Hi,
Thanks a lot for this advice. Do you know if I can still make 2 separate backups, so that I could use system backup if there's no FW change ?
Regarding the TWRP custom recovery, I understood that since I am already with FW 10.4.4.25 (android 4.1.1) and only rooted, there's no way to install customer recovery. Did I understood properly, or is there a way to downgrade to previous versions first, istall custom and upgrade again back to current FW ?
What do you mean by "tablet backed up to Google" ? I have "save my datas" checked under "backup" menu of parameters, but is there a way to check that there's indeed something in their servers already ?
br,
Ricorico94
Click to expand...
Click to collapse
I don't think it is a good idea to install a custom recovery if you are about to send the tablet to Asus - I assume for a warranty repair. You would have to unlock your bootloader and that negates your warranty. So just forgettaboutit.
Google backs up some of your data: Calendar and contacts mainly, but also all the apps you have downloaded or bought from the Play Store.
But it is much faster to restore apps with Titanium instead of downloading them from the Play Store.
So backup apps and data in TiBu and move the backup to your PC.
I don't quite understand why you want to backup system data. It's always potentially disruptive to mess with system data yourself. And you are on a pretty old rom and bootloader - so you're due for an update anyway.
Pictures, videos etc, I would just move to an external drive/card or your PC.
When you got everything backed up, do a Factory Reset. That will wipe your data partition.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Thanks to both of you for your help!
berndblb said:
I don't think it is a good idea to install a custom recovery if you are about to send the tablet to Asus - I assume for a warranty repair. You would have to unlock your bootloader and that negates your warranty. So just forgettaboutit.
Click to expand...
Click to collapse
You're right. I was asking this for future, when tablet comes back from repair: at that time, I might want to have a stronger debug/backup using a custom recovery (at least that's what I understood it's very helpful at): I'm soon at warranty end, so I can wait expiration.
It's a good news that the unlock tool of Asus can still be used to allow installation of custom recovery. I'll need to read more on how to do it, etc.
Thanks again !
Ok, so i'm new to all this stuff about custom recoverys and ROMs. How exactly do they work?
Let's say i make a custom recovery image of my current ROM, wich is stock, does it just backup the OS or my personal files (music, photos, apps, etc.) too?
I'm asking this primarly because i want to upgrade my phone, but to do so i have to flash the stock firmware because i've modified some system files. Wich bring to my other question, flashing ROMs wipe user data? i've read some split responses to this, some people say it does some say it doesn't.
And my final question, let's say i made a backup, wiped my phone flashed stock firmware and updated, now how i recover my data from the
backed up ROM, i mean it is a different version, does it have an option to just restore user data?
Thanks in advance, and sorry if these are too much questions.
it'll back up system, data, boot.img and dalvik cache.
your sd partition isn't backed up, but all the stuff on it will be readable by whatever new rom you put on it (unless you wipe EVERYTHING [not a good idea]).
when you're changing roms/etc, you want to place the rom.zip + gapps.zip (and custom kernel.zip if you're going to use one) on your sd partition. you do this because usb storage mostly doesn't work with custom recoveries as of yet on this device meaning once you've wiped, if you don't have a rom on your sd partition you're mildly screwed in that you'd have to reflash everything from a stock image (meaning you will lose root, all your personal files and whatever rom was on the phone - basically everything goes back to stock bar the bootloader).
e: as for restoring all apps data, use something like titanium backup. i always have a backup on my sd partition of all my current apps (plus wifi passwords, accounts info, sms messages etc to save time/effort when restoring after putting a new rom on). i also always set TB to backup all modified/new data every night at about 3am, then upload the backup to google drive so that if i either brick my phone or accidentally wipe everything, at least i can get back to where i left off.
If you forget to place the ROM zip, and have formatted the device, it is not necessary to flash stock. You use adb side load which is present in every recovery.
in that case i need to remember that for future use - i hardly ever use my pc with my phone now as you can pretty much do anything (update recovery etc) on the phone alone.
that, and i'm on windows 8.1 which afaik doesn't play nicely with fastboot or adb.
twist3d0n3 said:
....and i'm on windows 8.1 which afaik doesn't play nicely with fastboot or adb.
Click to expand...
Click to collapse
....i think this is a rumor. Never ever had any problems on W8.1
^ good to know, thanks
HOW TO BACKUP YOUR PHONE
Hey guys!
I've seen a lot of people being confused about how to backup your phone before a custom rom install or a firmware upgrade.
People here mostly use Titanium backup or Helium to use backup their phones, still the new users/noobs dont know how to operate them.
ao I am making a detailed guide for both, Rooted Phones and Non Rooted phones.
Thanks.
COMMON WAYS FOR ROOTED AND NON ROOTED :
CONTACTS : Simple. Android has given us the unique feature of backing up using the phone itself.
-Open the Contacts app
-Press the Menu Button
-Press Import/Export
-Export to SDCard
and youre done. The phone will make a *.vcf file in your system which can be used on any android phone.
IMAGES : Two Alternatives. Using an App or Manually
-App : Use Quick Backup to SD by Linever corporation from the playstore. It backups in the SD card by making a folder for each album that you've transferred.
MANUALLY :
-Copy the DCIM folder.
-Copy the Pictures folder
-Paste it somewhere safe
CALL LOGS : Use Easy Backup frim the playstore
SPECIFIC for NON ROOTED vs. ROOTED.
NON ROOTED PHONES
APPLICATIONS: TWO WORDS. APK EXTRACT from the playstore. IT saves your apps on the Internal SD card and then you can safely copy all your apps
APP DATA : The MOST IMPORTANT backup after contacts
Nobody likes to lose their HighScores or the points earned and start from the beginning.
-Download Helium App from the Playstore
-Download Helium App for the PC (it prompts)
-Enable USB Debugging from developer options
-Backup on the INTERNAL SD first.
-Copy the folder named CARBON from the internal SD to anywhere safe.
You can restore by the same app on some other phone by just pressing restore. Somehow for me I copy the carbon folder to the INTERNAL SD again and then restore as a direct restore from sd does not work.
ROOTED PHONES
We guys have a lot of options.
Ohh yes we do.
APPLICATIONS and APP DATA
Two APPS. TITANIUM BACKUP & HELIUM
-Open Tiranium Backup
-Tap Backup/Restore
-If you want to backup just one app, tap on it and select backup or;
to backup all the apps, use the tick mark in the app on the backup/restore tab.
Restoring Via TIB.
This is one issue many face. But it is simple.
-Just open TiB
-Press Menu button
-Press Batch Actions
-See for restore
-Press on Restore Apps with Missing Data.
HELIUM
The same process as non rooted users, but then we dont want USB debugging on or the Desktop app.
Just give root permissions and start backing up.
I find helium better than TiB for App and App data.
Again. Opinions differ
This is a basic guides for the "Important Things" in our phone.
If you want me to add about anything specific, Just leave a reply.
Or if you have any other ways or backing up, Ill add it here.
I'll make sure I keep this updated.
Thank you
PRECAUTIONS :
Never Backup system apps and try to push them on other roms.
Dont even try pushing them into system/app or system/priv-apps.
Each system app is made according to a relevant framework.
This can lead to a possible funny behaviour of the phone and many unexpected crashes and weird bootloops.
Its always advised to backup and restore the general utility apps that can be downloaded from the playstore to save data and download time
Do update backups once a week. This helps your backup not to get obsolete with time
Thanks @malybru for the help
[B]Guide for a NANDROID a.k.a. NAND backup.[/B]
Nandroid backups are a life saviour if you dont want to flash the whole stock rom then again do the process of custom recoveries etc. just because you had a "bootloop"
Like c'mon! A bootloop/random ui crashing and you flash a full stock rom. Sounds funny.
But yes, people have to do it if they dont have a handy nandroid backup.
Pre requisite:
-A Custom Recovery.
The best and widely used ones being Philz Recovery
TWRP Recovery
CWM recovery
(Will update links after sometime)
-Knowledge of how to flash things via odin.
-Some common sense on selecting what to flash
How to Install a Custom Recovery
Should I tell that?
in brief
1.Boot into download mode
2.Connect phone to odin and wait for odin to recognise
3.Select the recovery in AP/PDA
4.Press start and let it do its work.
How to enter into a custom recovery
a. Press Volume up + Home Button + Power Button. As soon as you see The GalaxyS4 screen, leave all three and in a jiffy press Volume Up + Home Button.
b. Use quickboot/any other mod that you run that boots your phone in recovery.
Nand Backup
a. When youre in the recovery, press on backup/restore
b. Press on backup and do a full system backup.
It usually takes 30 minutes for a bloated firmware backup. Restore takes the same time.
Do have atleast 40% battery.
Remember, backups can be selective too (Only Data/Only System etc etc.)
Same is for the restore.
A nand backup will always restore you to your last backup position (obvious). So do keep manual backups too.
Good guide.
Added to sticky roll-up thread.
thank you!
What about a basic nandroid backup?
Removed. Backup of messages is not available in stock sms app after all. Sorry for any problems my error may have caused...
jonahtriangle said:
What about a basic nandroid backup?
Click to expand...
Click to collapse
@jonahtriangle added the nandroid backup. Tell me if you want me to add more to it
"If someone helps, never forget to hit thanks ? "
@bobfrantic not an issue buddy
"If someone helps, never forget to hit thanks ? "
Anyone know how to backup bluetooth pairings? That causes me most pain when updating roms. Titanium has the feature but does not work
DeepankarS said:
HOW TO BACKUP YOUR PHONE
Hey guys!
I've seen a lot of people being confused about how to backup your phone before a custom rom install or a firmware upgrade.
People here mostly use Titanium backup or Helium to use backup their phones, still the new users/noobs dont know how to operate them.
ao I am making a detailed guide for both, Rooted Phones and Non Rooted phones.
Thanks.
COMMON WAYS FOR ROOTED AND NON ROOTED :
CONTACTS : Simple. Android has given us the unique feature of backing up using the phone itself.
-Open the Contacts app
-Press the Menu Button
-Press Import/Export
-Export to SDCard
and youre done. The phone will make a *.vcf file in your system which can be used on any android phone.
IMAGES : Two Alternatives. Using an App or Manually
-App : Use Quick Backup to SD by Linever corporation from the playstore. It backups in the SD card by making a folder for each album that you've transferred.
MANUALLY :
-Copy the DCIM folder.
-Copy the Pictures folder
-Paste it somewhere safe
CALL LOGS : Use Easy Backup frim the playstore
SPECIFIC for NON ROOTED vs. ROOTED.
NON ROOTED PHONES
APPLICATIONS: TWO WORDS. APK EXTRACT from the playstore. IT saves your apps on the Internal SD card and then you can safely copy all your apps
APP DATA : The MOST IMPORTANT backup after contacts
Nobody likes to lose their HighScores or the points earned and start from the beginning.
-Download Helium App from the Playstore
-Download Helium App for the PC (it prompts)
-Enable USB Debugging from developer options
-Backup on the INTERNAL SD first.
-Copy the folder named CARBON from the internal SD to anywhere safe.
You can restore by the same app on some other phone by just pressing restore. Somehow for me I copy the carbon folder to the INTERNAL SD again and then restore as a direct restore from sd does not work.
ROOTED PHONES
We guys have a lot of options.
Ohh yes we do.
APPLICATIONS and APP DATA
Two APPS. TITANIUM BACKUP & HELIUM
-Open Tiranium Backup
-Tap Backup/Restore
-If you want to backup just one app, tap on it and select backup or;
to backup all the apps, use the tick mark in the app on the backup/restore tab.
Restoring Via TIB.
This is one issue many face. But it is simple.
-Just open TiB
-Press Menu button
-Press Batch Actions
-See for restore
-Press on Restore Apps with Missing Data.
HELIUM
The same process as non rooted users, but then we dont want USB debugging on or the Desktop app.
Just give root permissions and start backing up.
I find helium better than TiB for App and App data.
Again. Opinions differ
This is a basic guides for the "Important Things" in our phone.
If you want me to add about anything specific, Just leave a reply.
Or if you have any other ways or backing up, Ill add it here.
I'll make sure I keep this updated.
Thank you
Click to expand...
Click to collapse
Mr. @deepankerS,
This guide makes life easy!
You mentioned to back up data and apps through APK Extract, Helium, TiB on the internal SD.
Can I do it on the external SD instead? Would that affect the restore process if i was to restore data and apps backed up on the external SD Memory card?
Ehabb1 said:
Mr. @deepankerS,
This guide makes life easy!
You mentioned to back up data and apps through APK Extract, Helium, TiB on the internal SD.
Can I do it on the external SD instead? Would that affect the restore process if i was to restore data and apps backed up on the external SD Memory card?
Click to expand...
Click to collapse
Lol first edit your comment and shorten the op thread
And yeah..if everything is on the internal sd, copy these folder manually from the internal to external. By default these apps will save info on the internal sd card.
Thus you have settings in the apks to select where to backup.
Just Helium doesnt work on extsd, be it backup/restore.
-TitaniumBackup
-Carbon (contauns helium data)
-ApkExtract/Extracted
Need some help, i have been making backups with recoverys TWRP and Phliz both. I did a full backup of my stock rom 4.4.2 and with TWRP when restore i was unable to write to internel sdcard. And ita was really a annoyn situation. And with the new Philz when i did the restore after boot all apps keep fc could not use it at all.
Any idea why this happens is it due to rong way of wipe (data, system, cashe) when i flash custom roms? Or way that i backup the stock rom? This only happens with the stock rom
Sent from my GT-I9505
DeepankarS said:
Lol first edit your comment and shorten the op thread
And yeah..if everything is on the internal sd, copy these folder manually from the internal to external. By default these apps will save info on the internal sd card.
Thus you have settings in the apks to select where to backup.
Just Helium doesnt work on extsd, be it backup/restore.
-TitaniumBackup
-Carbon (contauns helium data)
-ApkExtract/Extracted
Click to expand...
Click to collapse
Hello there @deepankers
I have rooted my phone and everything was going absolutely smooth until today I can't do anything to my external SD card (delete, create folder, etc...). I have already done the SD fix using the app "next app* when I first rooted the phone. I tried Uninstalling then reinstalling es explorer however the problem still exists! I'm sure that es explorer has root access. I tried using the stock "my files" app to do any modifications to my external SD however with no luck!
I appreciate your help in resolving this issue.
Kn!ght L!fe said:
Need some help, i have been making backups with recoverys TWRP and Phliz both. I did a full backup of my stock rom 4.4.2 and with TWRP when restore i was unable to write to internel sdcard. And ita was really a annoyn situation. And with the new Philz when i did the restore after boot all apps keep fc could not use it at all.
Any idea why this happens is it due to rong way of wipe (data, system, cashe) when i flash custom roms? Or way that i backup the stock rom? This only happens with the stock rom
Sent from my GT-I9505
Click to expand...
Click to collapse
i am facing the same issue using cwm 6.0.64 when i restore my stock rom backup and reboot lot of apps fc such as gapps but after some research in this forum i realize that only the latest philz recovery could backup and restore a stock rom properly
melekbarca said:
i am facing the same issue using cwm 6.0.64 when i restore my stock rom backup and reboot lot of apps fc such as gapps but after some research in this forum i realize that only the latest philz recovery could backup and restore a stock rom properly
Click to expand...
Click to collapse
I think the isuue is stock rom do a format to its partions which is why it do many isuues. Coz in reovery it do its own wipe before resotre. Which makes problems to stock.
Even in new philz i had the issue but what i did was wipe full (not internalsd) restore only system and boot once after that i restore data. In that way no isuue at all. All work good.
Sent from my GT-I9505
Kn!ght L!fe said:
I think the isuue is stock rom do a format to its partions which is why it do many isuues. Coz in reovery it do its own wipe before resotre. Which makes problems to stock.
Even in new philz i had the issue but what i did was wipe full (not internalsd) restore only system and boot once after that i restore data. In that way no isuue at all. All work good.
Sent from my GT-I9505
Click to expand...
Click to collapse
great idea i think that cwm 6.0.46 could get the job done using your method
Thanks
This was extremely helpful, i learned it super quickly.
Hi,
I'd like to recommend this app to backup SMS. I've used it a lot of times when changing ROMs, work pretty well. Also you can upload your backup to Dropbox, Google Drive, etc. and save it on External Storage. Quite useful .
~Lord
Hi there
Just need to backup the Efs partition easily... There is any method? Thanks so much
--
Believes in Christ and you and your family will be safe of the Great day of Jehovah's wrath
I9505 Powered with Phoenix Rom v9.4 - Tamirda
GoogyMax Kernel v1.1.5 - Googy_anas
Philz touch Recovery - Philz
S5's S-view Cover service - Karkasss
Jehovah's Thunder Bootanimation - Pas2001
Bootanimation sound - Me
A lot of mods and stuff - Xda community
Thanks to all of you...
Is there a way to perform a full backup via ADB?
Like a script or a line which creates a flashable full copy of one or all of the phones filesystems to PC.
Not(!)
adb backup -all
which backups merely system settings and not a migrate app which a) does not perform a full backup as it omits random files and b) works internal and neither TWRP backup-tool which only works internal.
andy01q said:
Is there a way to perform a full backup via ADB?
Like a script or a line which creates a flashable full copy of one or all of the phones filesystems to PC.
Not(!)
adb backup -all
which backups merely system settings and not a migrate app which a) does not perform a full backup as it omits random files and b) works internal and neither TWRP backup-tool which only works internal.
Click to expand...
Click to collapse
It can backup/restore your data, it can not backup your ROM/firmware, if you are not rooted, you will only be able to backup/restore user data, you will not be able to backup/restore any of your system apps/system app data, or any other part of system data and system settings, that will require rooting the device.
If you want a complete backup of the operating system and everything else on the device, you will need TWRP.
Sent from my SM-S767VL using Tapatalk
I am rooted. I am running TWRP.
I can't copy large amounts of data from inside the phone because something is buggy; this includes TWRPs backup-function. Copying works fine if and only if controlled by connected PC.
andy01q said:
I am rooted. I am running TWRP.
I can't copy large amounts of data from inside the phone because something is buggy; this includes TWRPs backup-function. Copying works fine if and only if controlled by connected PC.
Click to expand...
Click to collapse
Try flashing a newer or slightly older version of TWRP, it might fix the bugs that you are experiencing in TWRP. Is TWRP set to store your backups on external? Or is it set to store backups on your internal storage? Storing backups in internal takes up too much space, it's best to store backups on external.
As for adb...
https://forum.xda-developers.com/galaxy-nexus/guide-phone-backup-unlock-root-t1420351
There are several switches that can be used to be specific about what you want backed up and what you don't.
Sent from my SM-S767VL using Tapatalk
I updated to TWRP 3.4.0-0 (newest version) and backup from within TWRP still always fails between 20% and 30%. The last 30 to 40 backups failed and the only one that did finish to 100% is still broken and can't be read.
I would be thinking hardware-failure if not for the thing that copying anything from within the phone is super buggy, but copying when controlled from a PC works completely fine.
I guess I'll try the simple adb backup with some more parameters and then move on.
andy01q said:
I updated to TWRP 3.4.0-0 (newest version) and backup from within TWRP still always fails between 20% and 30%. The last 30 to 40 backups failed and the only one that did finish to 100% is still broken and can't be read.
I would be thinking hardware-failure if not for the thing that copying anything from within the phone is super buggy, but copying when controlled from a PC works completely fine.
I guess I'll try the simple adb backup with some more parameters and then move on.
Click to expand...
Click to collapse
How much free space do you have on internal storage? If there is less free space than your system, data and cache partitions combined, that may be why it is failing. Clear some space. I say this because when the backup is being created, the data that you want included in your backup is being read bit by bit from their partitions and then written into cache bit by bit and then it is read from cache bit for bit then it is written to its final storage location bit for bit. If there is not enough space to write it all into cache before writing it to its final location, it will fail.
The same rule applies when you move files from internal to external or vice versa, the same rule also applies when you are extracting files. It requires enough free space to write that data into cache before it goes where it is actually going.
Sent from my SM-S767VL using Tapatalk
Oh come on, I appreciate your efforts, but I felt being treated like a little child from your first answer and this tops it very much. Backup fails at 20-30% with 45GB of free internal space, external MicroSD removed and <10GB of data to backup. Aside from that I doubt that if a lack of free space causes the backup to fail, that this will not cause an error message to tell me what caused the fail.
By now I did the backups that I could backup:
That is I manually pulled all folders I deemed important.
Then I used "adb backup -apk -shared -all -system" which created a 7GB backup.
I also used the buggy migrate-app and ticked all boxes to get a 3GB backup.
And I used Googles cloud-service-backup.
In the end plenty of data and configurations were lost; worst is probably the Corona Warn App data as this can't be remedied.
andy01q said:
Oh come on, I appreciate your efforts, but I felt being treated like a little child from your first answer and this tops it very much. Backup fails at 20-30% with 45GB of free internal space, external MicroSD removed and <10GB of data to backup. Aside from that I doubt that if a lack of free space causes the backup to fail, that this will not cause an error message to tell me what caused the fail.
By now I did the backups that I could backup:
That is I manually pulled all folders I deemed important.
Then I used "adb backup -apk -shared -all -system" which created a 7GB backup.
I also used the buggy migrate-app and ticked all boxes to get a 3GB backup.
And I used Googles cloud-service-backup.
In the end plenty of data and configurations were lost; worst is probably the Corona Warn App data as this can't be remedied.
Click to expand...
Click to collapse
I can't help how you feel and you are entitled to feel however you wantl, but, at the end of the day, it is still only how you "feel", that doesn't make anything true or false. Just saying.
I didn't post anything to make you feel any kind of way, I was merely attempting to be as informative as I could because one can never gauge what someone else knows or understands before your interaction with them.
I've seen some other issues with TWRP backups failing and/or being unreadable, the solution is not a singular solution, there are several reasons why it fails and several fixes to solve it. Have you tried doing some google searches for:
"TWRP backups fail at 40%"
That pulls up some information that might apply or may not, you'll just have to peruse what you find to see if any of seems like it might be what you are experiencing and then try some of the solutions that others have tried. You might get lucky, you might not.
I'm more interested in helping you "find" an answer than whether I "know" the answer or "tell" you the answer.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Have you tried doing some google searches for:
"TWRP backups fail at 40%"
Click to expand...
Click to collapse
Yeah, I've done that for an hour or so before starting a thread - obviously b/c that has the chance for much quicker solutions and seems less work for me.
Also I did try several solutions like update TWRP, try smaller backups (the small ones do usually work) and so on. I think I did mention that I tried this over 40 times.
Some of the solutions suggest installing another ROM first, (apparently the ROM can cause Read-errors within TWRP?) but obviously I want the full backup before I try another ROM so I tried other methods to backup my data.
Also moving data via adb has worked completely without fail so far, so I wanted to try that path.
By now I can tell that TWRP full backup doesn't work on other ROMs either.
andy01q said:
Yeah, I've done that for an hour or so before starting a thread - obviously b/c that has the chance for much quicker solutions and seems less work for me.
Also I did try several solutions like update TWRP, try smaller backups (the small ones do usually work) and so on. I think I did mention that I tried this over 40 times.
Some of the solutions suggest installing another ROM first, (apparently the ROM can cause Read-errors within TWRP?) but obviously I want the full backup before I try another ROM so I tried other methods to backup my data.
Also moving data via adb has worked completely without fail so far, so I wanted to try that path.
By now I can tell that TWRP full backup doesn't work on other ROMs either.
Click to expand...
Click to collapse
Flash an older version or newer version of the exact same ROM as what you have but not doing any of the wipes, just flash ROM and that's it. This is called a "dirty flash", it will not wipe any of your data unless you specifically tell it to.
Alternatively, you could just do a backup via TWRP without including system and boot, just data and maybe cache(cache isn't necessary and might even cause issues if you restore it). Then, if you need to restore, flash the ROM the backup was created from then reboot to system, then boot back into TWRP then use "advanced restore" in TWRP to restore data and cache, this "should" give the same result as including system and boot in the TWRP backup along with data then restoring everything from that backup.
Also, can you post a copy of your recovery logs to some hosting site then link it here, someone here might be able to see something in the log that needs addressing, preferably the logs from the failed backup processes, if they errored in different ways, post the differences also. You should be able to find your logs if you haven't wiped the device.
Sent from my SM-S767VL using Tapatalk
Hello,
I just updated the rom Evolution X 11 on my Xiaomi Mi 9T Pro after using an older version for about half a year.
Now my phone does not boot anymore, its stuck in recovery (TWRP). Also all data seems to be encrypted and TWRP is not asking for a password.
Is there a way to get my phone to boot again or at least backup my data before I do a full wipe?
You should always do a full twrp backup before messing with roms.
The best solution would be to backup the "Data" and "Internal Storage" partitions. Data contains all apps, their appdata and settings, while internal storage contains all of your own files (photos, videos etc.). After you back these up, wipe your phone (system, data, cache, dalvik) and flash the version of evolution x you were using previously. Now restore data and internal storage and your device should be back to normal.
If you get a bootloop while booting after restoring data and internal storage, then wipe the device again and this time flash evolution x, but only restore internal storage. This way, it should boot and you will be able to recover your files, though your apps will be gone.
If you only restore internal storage then it will no doubt boot up and you will have access to your files, but since you'll have already backed up the important stuff (data + internal storage), you might as well try restoring data as well, as there is no harm, and if the phone boots correctly after restoring both partitions, your phone will be as it was before your updated your rom.
This happened a while back to me with my J5, the issue was that I made a full TWRP backup, then began to test other roms. After I was done, I tried to restore my backup, but it would constantly fail. I sat down for a while, confused and sad about how my TWRP backup had failed me. I tried every solution I could think of, eventually this solution I've mentioned in the above paragraph came to my mind. Thank god for putting it into my mind, otherwise I would've lost a lot of stuff (mainly whatsapp chats which werent backed up, and a lot of apps which I took the time to pain-stakingly configure in the best way for my device).
Anyways, enough of my story, hope this helps you out! If it does, message back here and let us know, and also mark my post as the solution if it was able to help you, so that anyone else who stumbles upon this thread can be saved too!
Cheers!
PhotonIce said:
You should always do a full twrp backup before messing with roms.
The best solution would be to backup the "Data" and "Internal Storage" partitions. Data contains all apps, their appdata and settings, while internal storage contains all of your own files (photos, videos etc.). After you back these up, wipe your phone (system, data, cache, dalvik) and flash the version of evolution x you were using previously. Now restore data and internal storage and your device should be back to normal.
If you get a bootloop while booting after restoring data and internal storage, then wipe the device again and this time flash evolution x, but only restore internal storage. This way, it should boot and you will be able to recover your files, though your apps will be gone.
If you only restore internal storage then it will no doubt boot up and you will have access to your files, but since you'll have already backed up the important stuff (data + internal storage), you might as well try restoring data as well, as there is no harm, and if the phone boots correctly after restoring both partitions, your phone will be as it was before your updated your rom.
This happened a while back to me with my J5, the issue was that I made a full TWRP backup, then began to test other roms. After I was done, I tried to restore my backup, but it would constantly fail. I sat down for a while, confused and sad about how my TWRP backup had failed me. I tried every solution I could think of, eventually this solution I've mentioned in the above paragraph came to my mind. Thank god for putting it into my mind, otherwise I would've lost a lot of stuff (mainly whatsapp chats which werent backed up, and a lot of apps which I took the time to pain-stakingly configure in the best way for my device).
Anyways, enough of my story, hope this helps you out! If it does, message back here and let us know, and also mark my post as the solution if it was able to help you, so that anyone else who stumbles upon this thread can be saved too!
Cheers!
Click to expand...
Click to collapse
Thank you for your help but backing up the data and internal storage doesnt seem possible right now because all the data is encrypted in TWRP...
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
PhotonIce said:
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
Click to expand...
Click to collapse
That sounds like a good idea. I found the old version on my PC.
Now I just need a way to install it... because twrp cant read the file. I tried with adb sideload but that results in an error for some reason. Flashing Magisk for example with adb sideload is possible.
Edit: Got it to work by using a tool called "Large Address Aware". Now waiting for the results...
PhotonIce said:
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
Click to expand...
Click to collapse
This did not help unfortunately... Im still in the same recovery-bootloop and my data is still encrypted.
It's probably still bootlooping as the data partition got modified when you flashed the newer version of evolutionx, and now it will not work with the old one. You can try wiping system+data+cach+dalvik and then flashing any rom of your choice. This will give you access to your internal storage (photos, media etc), but it will remove your apps and their settings. Whatsapp images are stored in the internal storage so you won't need to worry about those.
Again, this is risky, as it may not work (I don't know much about encryption), or you might still not be able to access your files after flashing the new rom. Proceed at your own risk.
PhotonIce said:
It's probably still bootlooping as the data partition got modified when you flashed the newer version of evolutionx, and now it will not work with the old one. You can try wiping system+data+cach+dalvik and then flashing any rom of your choice. This will give you access to your internal storage (photos, media etc), but it will remove your apps and their settings. Whatsapp images are stored in the internal storage so you won't need to worry about those.
Again, this is risky, as it may not work (I don't know much about encryption), or you might still not be able to access your files after flashing the new rom. Proceed at your own risk.
Click to expand...
Click to collapse
Thank you for still helping me out but I already did a full reset yesterday. I did not lose much except for the time setting it all up again.
I still dont really get the point of encrypting all your data if you cant decrypt it even if you know the password...