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
Related
Hello everyone, for starters im a complete newb at rooting phones and have never before tonight so please excuse my ignorance. I just rooted my phone which went fine, downloaded titanium backup and backed up everything, and then moved a zip of m1 cm10 and gapps onto my ext sd card. then i followed a video on how to install these. i was running clockwork recovery and did a factory reset/clear. in the video, the next screen had an option for "choose zip from sd", all mine had was something like update from external so i clicked that and it brought up my sd card files, including the cm10 and gapps files. i clicked on them (i tried each more than once) and they both stgarted to install then said failed. Im literally here freaking out because none of the apps i downloaded to restore my stuff are on my phone anymore, and when i downloaded them from the play store they said i had not backed anything up. somebody please help me, im legitimately having a nervous breakdown because i lost everything and dont know what to do.
Ok first things first. What was the fail error that CWM produced? I dont understand what you mean by none of the apps you downloaded to restore your stuff are on the phone anymore. Where did they go? If you didnt delete them they should still be there. Did you boot up after the failed attempt, and are now at a factory state OS? Perhaps titanium isnt pointed to the correct location of the backups you made. Please provide more info.
Edit: Ok I misunderstood a point. The apps I take it are gone from the factory reset, but I still dont understand why the backup data cant be restored.
Sounds like CWM didn't flash. That sounds like stock recovery. Flash factory image via Odin, reroot, and reinstall CWM. Download an app called EZ Recovery from the market and follow the instructions. You will be fine.
Sent from my SCH-I535 using xda premium
Just a side note as far as using CWM goes:
I've noticed that with CWM, the backup file sizes are way too small. Hence a possible corrupted backup folder. TWRP seems to work better with our device as far as backups go.
It's always a good idea to check the size of a backup afterwards before proceeding with any risky procedures like low level flashing. Luckily there is always ODIN.
With my device backup sizes range between 2.0GB and 2.34GB.
tekrhino said:
Just a side note as far as using CWM goes:
I've noticed that with CWM, the backup file sizes are way too small. Hence a possible corrupted backup folder. TWRP seems to work better with our device as far as backups go.
It's always a good idea to check the size of a backup afterwards before proceeding with any risky procedures like low level flashing. Luckily there is always ODIN.
With my device backup sizes range between 2.0GB and 2.34GB.
Click to expand...
Click to collapse
You've got to remember that CWM backs up differently now. It backs up data separately in blobs in a different folder. So your backups in clockwork are naturally smaller. Also, I've heard nothing but bad things with TWRP on this device. I'd stay away from it and stick with non touch CWM.
mustbepbs said:
You've got to remember that CWM backs up differently now. It backs up data separately in blobs in a different folder. So your backups in clockwork are naturally smaller. Also, I've heard nothing but bad things with TWRP on this device. I'd stay away from it and stick with non touch CWM.
Click to expand...
Click to collapse
This!
apacseven said:
Ok first things first. What was the fail error that CWM produced? I dont understand what you mean by none of the apps you downloaded to restore your stuff are on the phone anymore. Where did they go? If you didnt delete them they should still be there. Did you boot up after the failed attempt, and are now at a factory state OS? Perhaps titanium isnt pointed to the correct location of the backups you made. Please provide more info.
Edit: Ok I misunderstood a point. The apps I take it are gone from the factory reset, but I still dont understand why the backup data cant be restored.
Click to expand...
Click to collapse
When I open titanium backup and try to restore, it tells me no backups have been performed. Before trying to flash cm10, I moved the backup to my external sdcard and it is still there, yet I still can't restore it and when I try to do something with the files on my card it says no application can perform this task. Ive gotten my contacts back through tha app I backed them up on so I'm at a loss for why tb Isnt working.
levibernhardt said:
When I open titanium backup and try to restore, it tells me no backups have been performed. Before trying to flash cm10, I moved the backup to my external sdcard and it is still there, yet I still can't restore it and when I try to do something with the files on my card it says no application can perform this task. Ive gotten my contacts back through tha app I backed them up on so I'm at a loss for why tb Isnt working.
Click to expand...
Click to collapse
Launch titanium and hit menu/preferences. From there you can change the backup location to wherever you moved it to and it should see them.
Also for your contacts... If you are planning on flashing roms do yourself a favor a migrate your contacts off your phone and on to Google. That way you just log back in to your Google account after a re flash and they are all resynced. Plus you can access them from anywhere at contacts.Google.com
Sent from here using this
Relentless D said:
Launch titanium and hit menu/preferences. From there you can change the backup location to wherever you moved it to and it should see them.
Also for your contacts... If you are planning on flashing roms do yourself a favor a migrate your contacts off your phone and on to Google. That way you just log back in to your Google account after a re flash and they are all resynced. Plus you can access them from anywhere at contacts.Google.com
Sent from here using this
Click to expand...
Click to collapse
Did this ^ in titanium and the files show up, but it still says there is nothing to restore.
Also, could someone tell me/point me to a good method of flashing M1 cm10 onto a us cellular gs3?
mustbepbs said:
You've got to remember that CWM backs up differently now. It backs up data separately in blobs in a different folder. So your backups in clockwork are naturally smaller. Also, I've heard nothing but bad things with TWRP on this device. I'd stay away from it and stick with non touch CWM.
Click to expand...
Click to collapse
I agree 100%, the non-touch version of CWM works perfectly. I could care less about touch/non-touch/color of the app etc. ALL I care about is the capability to do a sucessful restore & CWM has never failed me for that.
I did a restore from it last night & it worked perfectly. The ONLY thing I have ever had to do after a CWM restore is clear data in GMAIL to get it to send.
Hi gents. I am trying to restore my phone to a recent clockworkmod recovery backup but several of the latest backups won't restore the downloaded programs of the time, nor do they seem to be restoring the general Android settings. Older backups are working perfectly, however, and I can't think of any significant or unusual changes I made to the system that could stop it working properly. Also, I have been backing up and restoring the same way.
I'm using Revolutionary CWM v4.0.1.4, HTC ICS 4.0.4 (w/ older HBOOT for S-OFF), HTC Desire S.
I find this very strange, and unsettling that clockworkmod's backup may be unreliable. Has anybody experienced this?
Another thing, I have also been backing up the entire SD card data in the later backups (just copying to computer via card reader), thinking it may be best to restore backups with this data, but it seems to not make a difference whether this is done, or the data left as-is, or the card cleared. What's best practice in regard to the Android data that's put on the SD card?
My phone is up the creek. Help!?
i am having the same problem restoring CWM v4.0.1.4 backups on my galaxy s2: older backups restore perfectly and newer backups restore incompletely (some settings and SMSs, but no apps and no contacts).
i believe this is an issue with large nandroid images (containing >10,000 files) being unable to restore properly. this implies the backup itself is intact, luckily.
read this:
http://forum.xda-developers.com/showthread.php?t=1154892
to rebuild my phone i started by using unyaffs on my PC to access the files on the CWM nandroid image and restore my contacts, call logs, etc:
http://forum.xda-developers.com/showthread.php?t=1370349
you can find additional file locations listed in this thread:
http://forum.xda-developers.com/showthread.php?t=969650
i then used appextractor (available in the play store) to manually restore my apps and app data from the CWM nandroid image. some needed to be redownloaded.
it's a schlepp but better than losing everything entirely.
i've read that TWRP is a more reliable way to backup and restore. i'm certainly not using CWM again.
regarding your second question, the data on your internal and external SD card is irrelevant to the function of the OS, but some apps may rely on that data. for example large apps install on the SD card.
Thanks so much for that matey. I searched and searched but hadn't come across the 10,000 files limitation. How annoying!
Anyhoo, before I saw your post I ended up restoring the latest working backup and reinstalled apps, configured things, got the device mostly up to speed.. but there were some sentimental Messages I wanted to restore. I got that unyaffs exe, the 10,000 file fix one, and managed to extract the mmssms.db just fine..
But I soon learnt it seems to be a nightmare to get it back into ICS because the SQLite db is in full-vacuum mode or some such, meaning it is cached and rewritten to help avoid fragmentation or some such. So I overwrite the mmssms.db, set permissions and ownership, reboot, and it's overwritten with the current one. Argh. I tried clearing cache. Tried running SMS backup/restore apps while the 'good' mmssms.db was in place, but they seem to look at the db cache/temp data, not the mmssms.db.
For those facing my situation and want Messages from CWM/nandroid backups in ICS, I found a great tip just posted on one of the threads N-acetyltransferase linked;
RichAP said:
I did this yesterday using Titanium Backup for my SMS/MMS
You need to go into Preferences and check the *Migrate system data [Experimental] option
Then you go to More - Extract from nandroid backup
There it is listed as Dialer Storage
Click to expand...
Click to collapse
I had tried using TiBu to restore Messages from nandroid backup (no success), but Dialer Storage!? How annoying. Anyhoo it's sorted.
Then I quickly found a good alternative recovery and quickly bought the premium version of 4EXT. It's very good, but get this, it actually recovered my latest CWM recovery backup no drama, just like that! Ahh well I didn't need those hours of my life anyway. I've often thought the Desire S's codename Saga is rather apt.
In conclusion, TiBu looks damn good and 4EXT is a ripper. I'd recommend it however the Galaxy S2 support is apparently unconfirmed thus far. Maybe look into it nevertheless.
Thanks for the help dude.
I'm trying to clear up a confusion in my mind about how to really backup a rooted Nexus 5.
(For privacy reasons I use a firewall, etc. and do not sync with Google or the cloud).
- I know that Titanium Backup will backup all the installed apps and their data.
- I know that a nandroid backup (I use twrp) will backup the android system and apps.
But there seems to be gap here - unless I am mistaken. Over time, most users add new folders in the sdcard for downloads, documents, genealogy, and the like. I tend to think of a nandroid backup as similar to an "image backup" in windows, but I suspect it might not be because the nandroid backup does not backup these newly created folders. Am I correct? Does a nandroid backup these additional sdcard folders? I think most people assume they do, but a friend just told me they do not and he lost a lot of data because of that erroneous assumption. I hope he is wrong!
Does a nandroid backup the system and the entire sdcard - or not? If not, why not? I'm not a programmer but it would seem to be a simple thing to include any additional sdcard folders? What am I missing? Is there a technical reason why a complete backup is not possible in android?
A nandroid doesn't backup 100% of the device.. I'm not sure why, but I know it doesn't. /sdcard (or whatever its called lol) is not backed up.
Sent from my Nexus 5 using Tapatalk
You're correct that there is no simple way to back up your entire device. Even using Google will not back it up.
A nandroid will back up your system, apps and app data. It will not backup your /sdcard. That means any photos, music, downloaded files, etc.
Unfortunately, to backup your device you really need to use a nandroid, the cloud and your pc.
Sent from my Nexus 5 using XDA Free mobile app
That's a shame. I was hoping I was wrong! I bet a lot of users have been burned by that! :crying:
Seems to be a glaring opening for a "killer app" that would
a) reboot the phone into recovery
b) do a nandroid backup
c) append a backup of remaining folders
Then the whole could be copied to a pc or flashdrive. Maybe even done in one swoop while attached by usb to a pc. Like a pc backing up an image to an external hd - which I do all the time.
It's so obvious that I wonder what is making this unachievable in android.
Is there such an app? Looks like I have been living dangerously.......
If you could do that you'd run out of storage space before it completed
Sent from my Nexus 5 using Tapatalk
I just create a folder called backup on my comp. Then do a:
Code:
adb pull /. backup
It takes two hours but pulls the entire phone to my comp. Or at least as close as you'll ever get with android.
Ben36 said:
If you could do that you'd run out of storage space before it completed
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I thought of that. That is why it would be an app to run while your device was connected to the pc. Just like when I do an image backup of my windows laptop to an external HD.
You need to connect to a PC or other drive to transfer the nandroid anyway.
theesotericone said:
I just create a folder called backup on my comp. Then do a:
Code:
adb pull /. backup
It takes two hours but pulls the entire phone to my comp. Or at least as close as you'll ever get with android.
Click to expand...
Click to collapse
That is what I will have to do. Thanks for the adb command to use.
But, it is a two step procedure: first create a nandroid, then connect to PC to move everything there. Unless I am wrong, without a nandroid, just copying everything on the phone will not let me restore the system. (Maybe I am wrong).
I am not knowledgeable enough, but, if not an app, maybe a script that you run - while connected to the PC (or external HD? with stickmount?) - would either boot the phone into recovery, do the nandroid, and copy everything (including the nandroid) to the pc. Unless one can skip a step by creating the nandroid directly on the PC instead of on the phone.
I'm a relative newbie and could be talking nonsense - sorry if I am - but if it can be done in Windows, it should be abe to be done in android/linux.
maybeme2 said:
That is what I will have to do. Thanks for the adb command to use.
But, it is a two step procedure: first create a nandroid, then connect to PC to move everything there. Unless I am wrong, without a nandroid, just copying everything on the phone will not let me restore the system. (Maybe I am wrong).
I am not knowledgeable enough, but, if not an app, maybe a script that you run - while connected to the PC (or external HD? with stickmount?) - would either boot the phone into recovery, do the nandroid, and copy everything (including the nandroid) to the pc. Unless one can skip a step by creating the nandroid directly on the PC instead of on the phone.
I'm a relative newbie and could be talking nonsense - sorry if I am - but if it can be done in Windows, it should be abe to be done in android/linux.
Click to expand...
Click to collapse
Honestly the only time I've used that command was a few years ago when I was looking into what your asking about. Long
story short, it was a complete failure. lol The best bet is just using a nand and copying your sdcard over to the comp whenever you feel the need. It's really easy to restore the sdcard. It's really hard to use ADB to restore anything else. It's possible but takes way more time than just restoring a nand.
Hi, 2 days ago with the help of App Inspector and MiXplorer i was debloating my phone from all those useless apps like Huawei ID, HiCare, Swiftkey, ecc. and while I was doing it i took the chance to remove some other service packages that I'm sure I'd never used in future, like Geofence, Mapcon, Fido client, ecc. Everything worked nice in the phone, overall because obviously i paid an extreme caution while removing packages since that we're talking about system files, and i fact i didn't noticed incompatibilities or other issues while using the phone in these 48h.
The only problem that i encountered is that now my TWRP isn't able to restore a nandroid backup without getting a failure accompanied by the error mentioned in thread title.
Code:
[COLOR="red"]extractTarFork() process ended with ERROR: 255[/COLOR]
When i reboot to system however, everything is fine except the theme that i have to set again, the list of previous SMS empty (but i have contacts, system settings, apps, notes, everything else) and a leftover of Swiftkey app that i have to remove again. I tried with 2 different backups: one made before debloating the phone 2 days ago, and the second is a backup took today on the phone already debloated. Anyway making some searches around i found this topic https://github.com/TeamWin/Team-Win-Recovery-Project/issues/964 in which i read that a possible cause could be the amount of free space on the phone, but i have more than 17GB free and I'm restoring the backup from external SD, so i can exclude for sure this cause... Another solution standing by what i read elsewhere could be to unmount the "data" partition on the phone before restoring the backup, but neither that changed a single thing and i keep getting the same error. I think that what could provoke this issue is related to some files linked to missing apks, like data of an app removed but it's the only clue i have about now.
I hope that someone can really help me out on this because TWRP backups for me are essential. Looking forward for your answers guys! Any help will be extremely appreciated!!
EDIT: i can provide logs obviously if someone could be able to detect the error by reading them, i can't so let me know if someone would like to dedicate some minute on reading a log
Other things noticed: i had to reflash again Magisk Modules and even Magisk V14.3 zip to being able to flash modules stored on my SD, even if Magisk was still installed. This is surely due the fact that the restore of data partition started and then it got stopped by fault of error 255, so data partition wasn't fully restored. The thing that i just can't understand is why even the older backup isn't working, maybe I'll have to format data dalvik and cache to get the older backup working..? Damn
Bump. C'mon guys, really no one??
RedSkull23 said:
Bump. C'mon guys, really no one??
Click to expand...
Click to collapse
Haven't seen yet bro
shashank1320 said:
Haven't seen yet bro
Click to expand...
Click to collapse
Dammit that's bad, i known from beginning that it's a complex issue but i thought that someone here could help...
RedSkull23 said:
Other things noticed: i had to reflash again Magisk Modules and even Magisk V14.3 zip to being able to flash modules stored on my SD, even if Magisk was still installed. This is surely due the fact that the restore of data partition started and then it got stopped by fault of error 255, so data partition wasn't fully restored. The thing that i just can't understand is why even the older backup isn't working, maybe I'll have to format data dalvik and cache to get the older backup working..? Damn
Click to expand...
Click to collapse
May be you need to format data, dalvik and cache and then reboot to recovery again from recovery.
I am facing such issue these days and had to opt for this to mount data again. Never understood this concept with huawei phones. my old Yu Yureka was hell easier to flash all these.
shashank1320 said:
May be you need to format data, dalvik and cache and then reboot to recovery again from recovery.
I am facing such issue these days and had to opt for this to mount data again. Never understood this concept with huawei phones. my old Yu Yureka was hell easier to flash all these.
Click to expand...
Click to collapse
The only thing that stops me from trying to solve this by wiping data, dalvik and cache is that if after wiping the issue will persist, other than not being able to restore my backup I'd find myself with a phone where i have to restart from scratch too. And so it could be even worse... I really don't know what to do at the moment, but i must fix this.
RedSkull23 said:
The only thing that stops me from trying to solve this by wiping data, dalvik and cache is that if after wiping the issue will persist, other than not being able to restore my backup I'd find myself with a phone where i have to restart from scratch too. And so it could be even worse... I really don't know what to do at the moment, but i must fix this.
Click to expand...
Click to collapse
May be a twrp backup... once all restored then restore data
So, some day ago i managed to solve my problem trying once again to restoring a copy of a TWRP backup, this time an older one dated 2 weeks ago other than 1 like the previous backup... (for safety reasons i always keep 2 backups, and i overwrite these weekly one after another, by the most recent) and this time it worked. I seriously can't understand why this error happened only on the 1st and more recent backup, since that i started to debloat some system apks and packages only 1 week after the latest backup, and so without system modifications the error shouldn't have to be already present on the backup took exactly 1 week before starting to remove files... but i'm out of this now
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...