So i think my nandroid backup is nuked... i do a wipe/factory reset, wipe the cache etc etc - tried restoring the backup. After 10mins or so of waiting the process completes and i reboot the phone. I have been sitting here for over 1hr looking at the boot animation.
If there is noway to restore the ENTIRE backup, is there a way i can extract specific stuff like my text messages? I really can't afford to lose them
duwii said:
So i think my nandroid backup is nuked... i do a wipe/factory reset, wipe the cache etc etc - tried restoring the backup. After 10mins or so of waiting the process completes and i reboot the phone. I have been sitting here for over 1hr looking at the boot animation.
If there is noway to restore the ENTIRE backup, is there a way i can extract specific stuff like my text messages? I really can't afford to lose them
Click to expand...
Click to collapse
That seems to happen when /datadata is full or there's some other problem with restoring /data, and the system isn't able to boot. Maybe you can wipe /datadata only and see if boots. I also know that TiBu can extract data from nandroid backups, but I'm not positive whether that applies to messaging.
korockinout13 said:
...Maybe you can wipe /datadata only and see if boots...
Click to expand...
Click to collapse
Let me apologize for my ignorance but how do i do that?
duwii said:
Let me apologize for my ignorance but how do i do that?
Click to expand...
Click to collapse
In recovery, go to mounts & storage, and format /datadata. Although my memory fails me as to where messages are stored...
Sent from my SGH-I897
i forgot to mention that this is a fresh installation (i formatted the entire internal storage, basically coming from STOCK).. i still need to do that wipe you refer to?
duwii said:
i forgot to mention that this is a fresh installation (i formatted the entire internal storage, basically coming from STOCK).. i still need to do that wipe you refer to?
Click to expand...
Click to collapse
Well wiping /datadata may (or might not) allow the phone to boot, because the phone can't boot when that partition is completely full. It also might wipe your messages but I'm not positive.
Related
Hi all.
I've been doing backups of my Nexus 5 with TRWP. I chose all options, that is I added 'cache' and 'recovery'.
Question: Is that bad? Should I not backup those?
Thanks.
Just use the ones it defaults to, system, data, boot. You don't need to backup the others. same with wipe, just use the slider thing. Messing with the others can get you on trouble
One other thing, make one backup of the efs only and store that in a safe place off your phone
jd1639 said:
Just use the ones it defaults to, system, data, boot. You don't need to backup the others. same with wipe, just use the slider thing. Messing with the others can get you on trouble
One other thing, make one backup of the efs only and store that in a safe place off your phone
Click to expand...
Click to collapse
Can I recommend having 2 different efs backups on the phone and a copy of each off the phone?
That way you're mitigating the risk of one backup being incomplete and the risk of corruption through transferring the files "offsite"
Sent from my Nexus 5 using Tapatalk
Wow. So it is indeed bad. Why?
What i did:
Backup01: Restore phone to defaults, root, backup of all (including cache and recovery).
Backup02: Configure my phone, backup of all (including cache and recovery).
Backup03: Install apps, backup of all (including cache and recovery).
Should I restore to each of them and make a new backup without cache and recovery?
Thanks.
jd1639 said:
Just use the ones it defaults to, system, data, boot. You don't need to backup the others. same with wipe, just use the slider thing. Messing with the others can get you on trouble
One other thing, make one backup of the efs only and store that in a safe place off your phone
Click to expand...
Click to collapse
rootSU said:
Can I recommend having 2 different efs backups on the phone and a copy of each off the phone?
That way you're mitigating the risk of one backup being incomplete and the risk of corruption through transferring the files "offsite"
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
rwed said:
Wow. So it is indeed bad. Why?
What i did:
Backup01: Restore phone to defaults, root, backup of all (including cache and recovery).
Backup02: Configure my phone, backup of all (including cache and recovery).
Backup03: Install apps, backup of all (including cache and recovery).
Should I restore to each of them and make a new backup without cache and recovery?
Thanks.
Click to expand...
Click to collapse
What you did isn't bad, it's just the backups will be larger and they have information in them you don't need. Recovery is your twrp recovery and the cache will be recreated when you boot your device
jd1639 said:
What you did isn't bad, it's just the backups will be larger and they have information in them you don't need. Recovery is your twrp recovery and the cache will be recreated when you boot your device
Click to expand...
Click to collapse
OK I see. Then can I just keep those backups with all efs, cache and recovery included? May it lead to problems in future restores?
Thank you!
rwed said:
OK I see. Then can I just keep those backups with all efs, cache and recovery included? May it lead to problems in future restores?
Thank you!
Click to expand...
Click to collapse
You should be ok. The one thing you never want to do is restore an efs partition from one phone onto another phone. That is an instant hosed phone that you can't recovery from.
jd1639 said:
You should be ok. The one thing you never want to do is restore an efs partition from one phone onto another phone. That is an instant hosed phone that you can't recovery from.
Click to expand...
Click to collapse
Yes... I'm reading several articles on that! Pretty scary... I'm gonna do as rootSU suggested and make 2 different backups and store 2 copies offsite, somewhere cloud-based...
I'll then keep these backups I made with all selected. With your first post I thought... I don't know... that maybe restoring these images with all recovery, cache and efs might lead to problems when booting.
If I understand correctly, this is not the case, I just misunderstood you, what you meant is that "it doesn't hurt, it's just not needed", right?
Thank you jd!
Ok, I have done my research and this is a common problem with a new flash, and it happened to me, but I didnt notice it until now. I have the 32 gig nexus, and its only utilizing half of that.
Is there any way at all to correct this without having to wipe everything? I have my phone setup like I want it, and it took a bit of workarounds with lollipop with viper and all.
Or can I at least just make a nandroid? and back up that file somewhere, and then reflash everything or do a wipe to get my space back, and then restore that nandroid? Or will that nandroid bring back the space problem?
Thanks
No. You have to wipe everything. Its the only fix.
Nandroid shouldn't cause an issue. Storage is the issue and nandroid doesn't back up or restore storage.
joho5 said:
Ok, I have done my research and this is a common problem with a new flash, and it happened to me, but I didnt notice it until now. I have the 32 gig nexus, and its only utilizing half of that.
Is there any way at all to correct this without having to wipe everything? I have my phone setup like I want it, and it took a bit of workarounds with lollipop with viper and all.
Or can I at least just make a nandroid? and back up that file somewhere, and then reflash everything or do a wipe to get my space back, and then restore that nandroid? Or will that nandroid bring back the space problem?
Thanks
Click to expand...
Click to collapse
You can wipe userdata via fastboot and fix this issue.
Jnewell05 said:
You can wipe userdata via fastboot and fix this issue.
Click to expand...
Click to collapse
This won't touch my internal SD right? So my backup would be safe? Could wipe userdata and then restore backup?
Thanks for taking the time to help.
Sent from my Nexus 5 using XDA Free mobile app
joho5 said:
This won't touch my internal SD right? So my backup would be safe? Could wipe userdata and then restore backup?
Thanks for taking the time to help.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You HAVE to wipe your "internal SD"
Take a nandroid, backup ALL your data to PC.
rootSU said:
You HAVE to wipe your "internal SD"
Take a nandroid, backup ALL your data to PC.
Click to expand...
Click to collapse
Which wipe command will wipe all of this?
I am comfortable using adb/fastboot or whatever, but just need to know how to completely wipe it all.
Can I just redo the factory image flash, like i did initially?
joho5 said:
Which wipe command will wipe all of this?
I am comfortable using adb/fastboot or whatever, but just need to know how to completely wipe it all.
Can I just redo the factory image flash, like i did initially?
Click to expand...
Click to collapse
Use fastboot to erase and then flash userdata.img (not whole factory image)
formatting the userdata did the trick...thanks guys.
much appreciation.
Welp, new problem...knew it couldnt be quite that easy.
I copied my whole TWRP folder with the backup inside to my pc, now I cant copy it back. It gives me an immediate error saying it cant copy.
I can click into the folder and copy and paste just the backup folder onto my device, but how can I restore a backup from a custom location, because since twrp doesnt see the TWRP/Backups exact path, then I see no backups to restore from.
Is there a way to restore from say like just sd/backups?
So I recently flashed Paranoid Android based on Lollipop 5.1. Everything was working perfectly but I decided I wanted to flash Xperience kernel. I did a nandroid backup first. I flashed Xperience. After going into a bootloop I went back to TWRP to restore and retry to see what I did wrong. After restoring I am cought in a bootloop again. What should I do?
Try wiping cache and dalvik cache.
bhatt095 said:
Try wiping cache and dalvik cache.
Click to expand...
Click to collapse
Already tried that. I already got it to boot but I lost all my apps and stuff so that sucks. I am still trying to make the restore work because I am lazy about downloading everything again configuring and personalizing my device again.
ekuhlmann said:
Already tried that. I already got it to boot but I lost all my apps and stuff so that sucks. I am still trying to make the restore work because I am lazy about downloading everything again configuring and personalizing my device again.
Click to expand...
Click to collapse
have you backupd all the stuff (/data /system /boot ) ??? thats really all that need. wiping cache means no real data loss. if yes, then wipe the phone complety( format /sytsem /data /cache /dalvik /internal storage) (maybe copy internl storeage on pc 1st) to make sure all is fine from phons side. after that restore your backup completly but without restoring cache & try to boot.
bejunk said:
have you backupd all the stuff (/data /system /boot ) ??? thats really all that need. wiping cache means no real data loss. if yes, then wipe the phone complety( format /sytsem /data /cache /dalvik /internal storage) (maybe copy internl storeage on pc 1st) to make sure all is fine from phons side. after that restore your backup completly but without restoring cache & try to boot.
Click to expand...
Click to collapse
I did not backup everything. I only backed up what was checked by default on TWRP so that is probably it. Thanks.
ekuhlmann said:
I did not backup everything. I only backed up what was checked by default on TWRP so that is probably it. Thanks.
Click to expand...
Click to collapse
i think TWRP atleast backups /system , /data & /boot maybe u check it? (you can tap on cutom restore or look in the backup folder to know whats bacupd)
bejunk said:
i think TWRP atleast backups /system , /data & /boot maybe u check it? (you can tap on cutom restore or look in the backup folder to know whats bacupd)
Click to expand...
Click to collapse
Damm I am so stupid. Apparently I accidentally unchecked boot so it wasnt backed up. That is most likely the reason why I am not booting.
ekuhlmann said:
Damm I am so stupid. Apparently I accidentally unchecked boot so it wasnt backed up. That is most likely the reason why I am not booting.
Click to expand...
Click to collapse
Ok then its easy. Wipe the Device, install only the Rom which has the needed kernel, Boot it once, then back to recovery & restore System + Data. Done =) good luck
Btw /Boot is the kernel. So you never restored your old kernel and spirit bootlooped like you say...
bejunk said:
Ok then its easy. Wipe the Device, install only the Rom which has the needed kernel, Boot it once, then back to recovery & restore System + Data. Done =) good luck
Btw /Boot is the kernel. So you never restored your old kernel and spirit bootlooped like you say...
Click to expand...
Click to collapse
Still bootloop. I am giving up. Starting over.
Hi, I'm a bit new to Nandroid Backup, so when you click backup in TWRP then there is "Partitions to Backup" options. I read a guide that you have to check Boot, System, and Data. The thing is, can I just backup System and Boot? And when I restore them does my phone will gone wrong?
Thanks
• Boot is to start the phone up. This is always needed.
• System is for the ROM. This is always needed.
• Data is for your installed apps and settings. Basically, if you backup and restore this, it will be like you used a time machine.
Every data backup is for its own ROM! Do not ever try to restore a data backup from a different ROM!
• Cache is basically the cache. It is not needed, but you can. It speeds up the startup after restoring. If you don't backup it, it will be recreated anyway but you have to wipe your old cache first otherwise they will conflict.
UnexpectedGuy said:
Hi, I'm a bit new to Nandroid Backup, so when you click backup in TWRP then there is "Partitions to Backup" options. I read a guide that you have to check Boot, System, and Data. The thing is, can I just backup System and Boot? And when I restore them does my phone will gone wrong?
Thanks
Click to expand...
Click to collapse
Backup
System
Boot
EFS
DATA
this would be sufficient and will nt cause changes or harm to your phone when you restore
********************Hit Thanks if i Helped*********************
Gautam Maini said:
Backup
System
Boot
EFS
DATA
this would be sufficient and will nt cause changes or harm to your phone when you restore
********************Hit Thanks if i Helped*********************
Click to expand...
Click to collapse
thanks, that's what I need.
Letzen said:
• Boot is to start the phone up. This is always needed.
• System is for the ROM. This is always needed.
• Data is for your installed apps and settings. Basically, if you backup and restore this, it will be like you used a time machine.
Every data backup is for its own ROM! Do not ever try to restore a data backup from a different ROM!
• Cache is basically the cache. It is not needed, but you can. It speeds up the startup after restoring. If you don't backup it, it will be recreated anyway but you have to wipe your old cache first otherwise they will conflict.
Click to expand...
Click to collapse
also thank you @Letzen, very helpful :good:
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...