Database Info

Unfortunately, the process com.android.phone has stopped.

As per my title, I'm getting this error message constantly after restoring my most recent backup of CM9 RC2. This was shortly before I started testing other ROM's (Hydro and CleanROM). The message comes back every single second, and I can barely get taps inbetween. Shutting the tablet off is a chore.
There are numerous threads on this error but they are all problems occurring on phones, not tablets, so I felt it appropriate to re-post. Any ideas to get this to go away? I don't have another recent backup so I'd like to be able to fix this without having to re-do all my work
Pertinent information:
Was using TF300T with CM9RC2 beforehand. Made nandroid backups, began testing other ROM's that required me to revert back to stock a few times. Have already tried restoring backup after factory reset, with cache and dalvik wiped. Pushing files to tablet on a Windows 7 PC using ADB, and everything on that end works fine. Also, if I dismiss the com.android.phone error, there are a number of other processes that have stopped working in the background as well, so the tablet is unusable.
Thanks,
Opethfan89

I've got a minor update to this issue, in that I decided to poke around in one of the backups that I know is a working backup, and found where the com.android.phone process is located (the /data partition, I guess).
So my question becomes, is there a way for me to manually load a nandroid backup and select/choose which files I restore from which folder? So if I get a com.android.phone folder from one backup and combine it into the backup that is messing me up, would that potentially work?
Also, how do I get access to the /data, /cache and other partitions on my tablet? Can I browse them through Windows Explorer or do I have to use Root Explorer on the tablet?

It's been four days, *BUMP*? Any responses?

My suggestion is do a clean install of the rom you want, forget about the backups and see if it works with a fresh install
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

While installing different roms on my device i learned to always do a full delete of cache, delvick cache, factory and last system. Always did it in that order. Maybe there is not very much logic to it since system will do all of it but that's what i did. I'm not sure what kind of recovery your using but I would recommend TWRP, but i doubt that's the issue.
Hope this helped

Thanks for the responses, guys.
I was not able to find a resolution to this error code or why it pops up, but I was able to salvage my install. My titanium backup from the 29th (before this error message was on my nandroid backups) was able to save all my apps, the layout, etc. I had to sit there for 3 hours manually allowing each and every app to install, but thats much better than trying to piece together which apps I had and what order they were in.
That being said, I'm now in the habit of making almost daily nandroid backups and titanium backups, as well as backing up any/all settings at every opportunity.
In response to the last post, I use CWM and I thought I clarified that in my original post. Not sure how/why the backups got corrupted, but I don't blame the recovery.

i get this fc when i change my sim with any other network sim card,maybe the phone has network lock?

[Q] Which app to restore apps/settings after installing ROM?

I installed B145 with the kat 80b kernel and the v3 battery patch and everything looks good. I had to swipe as I was using build 81 before. Quite honestly, since I'm not running any synthetic benchmarks nor overclocking the proc, I'm hard pressed to find any difference in performance from EOS 3. Mind you, the buttery feel on this ROM (and EOS 3, for that matter) is day and night when compared to Asus's stock code. So if you're like me and waited this long to root your Transformer (I popped its cherry just a month ago, after having it for 1 year), don't be afraid to try this ROM... the best thing to have happenned to the og transformer.
One question I have is, what are you guys using to constantly restore your apps and/or settings after repeatedly flashing new ROMs? It's a pain in the neck having to reinstall all the apps and setting them up! Thank you and special thanks to Timduru and his minions This thing is awesome...
Sent from my Transformer TF101 using Tapatalk HD

I use Titanium Backup, but I let Google install all my apps, then restore the data.
There are a few apps I have to install using Titanium (from Amazon) that I have to restore using Titanium. Those apps I have to tap the Install button and Done for each one.
I tried using the App Backup in the ROM Toolbox by Jrummy, but it did not restore all the data correctly (mainly thumb keyboard).
I also make nandroid backups using TWRP so I can quickly restore a working ROM without having to reinstall stuff if something goes south.

I also use Titanium Backup but with some reservations. If you're going to go back to the ROM you're running, you're much better off with a nandroid backup. TB is cool for a few reasons: batch backup/restore, system apps or just apps, etc... however you have to be careful with it.
- Make sure you always verify your backups (often). Never assume "they'll work", cause they most likely won't - that's a known issue that it fails to parse its own packages once in a while, so batch restores just lock up the entire operation and you have to forcibly kill it to start where it left off.
- Always keep a copy of the backups elsewhere than on the tablet
- Just because it backs up a system app or an app doesn't mean it can restore it, even on the same rom.
- Some stuff like contacts need to be exported then imported back especially if you're upgrading to another android version.
- System apps will almost always fail to install on another android version unless they were "hacked" to make them work.
So yeah it's a really good and powerful tool but to use with caution. Always redo full backups and verify them before you wipe/flash and always have a complete nandroid backup to restore in case of issues, like Frederuco said.
Edit: Once you're on Team EOS's roms, I dount think you have to do a full wipe anymore. I just wipe cache, dalvik and system, then flash the new rom, that way all my apps are still there. I only do a full reset if I experience issues after doing this, to make sure it's the rom and not apps, and to report to Tim from a fresh flash.

Thank you both. I'll give Titanium a try whenever I try another ROM. In the meantime I decided to go back to EOS3 build 81. I *really* don't like the new status bar on top. It specially bugs me when browsing the web since it's eating up screen real estate.
[Edit]
This is probably a known issue, but for those going back from EOS 4 to EOS 3: the directory /sdcard was copied to /sdcard/0 after installing EOS 4; so, when I restored EOS 3 from nandroid backup, the system wasn't responding as it should and some apps were very slow (I guess expecting to find their data under /sdcard). Copying /sdcard/0 back to /sdcard and rebooting made everything work much better. Thanks.

landous said:
[Edit]
This is probably a known issue, but for those going back from EOS 4 to EOS 3: the directory /sdcard was copied to /sdcard/0 after installing EOS 4; so, when I restored EOS 3 from nandroid backup, the system wasn't responding as it should and some apps were very slow (I guess expecting to find their data under /sdcard). Copying /sdcard/0 back to /sdcard and rebooting made everything work much better. Thanks.
Click to expand...
Click to collapse
From what I've read this is an issue with CWM. I saw frederuco mention it on the EOS 4 thread.
I had the same problem, went from build 92 to preview 145 and Titanium Backup couldn't find anything. I was pulling my hair out until I saw his post

If you use TWRP 2.3.2.3 the /0 directory issue goes away.
Also, TWRP IMO is much better than any CWM to date.

[Q] Restore nandroid backup

Hello Guys,
Since I totally bricked my old Nexus 5 16GB(KTU84P) I am going to get a new one. But I am thinking of getting the 32GB version this time.
Now before it got bricked I made a full nandroid back-up with the help of the Nexus Root Toolkit and TWRP.
Now here are a few (stupid) questions:
~Is it possible to restore a nandroid backup from one phone to another and even in this case a "different" version of the phone?
(I've skipped over this thread real fast http://forum.xda-developers.com/showthread.php?t=728266 which says it is possible for phones of the same model)
~If it is possible how should it be done?
~And well if the first question isn't possible, is there a way to read out out the created back-up files which TWRP created and manually restore them(preferable the data partition)
I hope you guys can help me out
Kind regards

Yes, you can do it. Just make sure you're not restoring the efs partition or you'll have another brick on your hands.
Sent from my Nexus 5 using XDA Free mobile app

Also don't use toolkits next time. Please use the manual methods which are better, safer and teach you the basis you need to recover.
All guides and info threads can be found in general > sticky roll-up thread
Sent from my Nexus 5 using Tapatalk

When you run into issues, as many do after nandroid restoring from one device to another... Wiping and Flashing stock with fastboot is the Fix.
Thought I'd cover that up front. ?

jd1639 said:
Yes, you can do it. Just make sure you're not restoring the efs partition or you'll have another brick on your hands.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
rootSU said:
Also don't use toolkits next time. Please use the manual methods which are better, safer and teach you the basis you need to recover.
All guides and info threads can be found in general > sticky roll-up thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey guys sorry I didn't answer immediately, but after I saw the posts I immediately ordered a new Nexus 5 (32GB this time). I got it delivered today and like you said I've done the unlocking, custom recovery and rooting manually this time instead of using a toolkit. Which was to be honest way easier than I thought but also way faster than using a toolkit.
But now I've kinda run into a other 'problem'
When I restore my previous made backup (the one from the bricked phone) I first of all only get the options to restore the 'system' partition and the 'data' partition (which is totally fine cause those are the only ones I actually need).
But when I restore the system partition a lot of apps crash on default(It is basically bricked then), and even when I just restore the data partition the same thing happens. (To be completely fair this problem might come from the fact that I used the MD5 verification option when I made the backup but I can't really remember that. but some of my backup files end with the .MD5 extension) Saying this I also used the restore option with check MD5 verification, but needless to say I get the message that they verifications don't match.
So here are a few questions again.
~Like I said before I only really care about the 'data' partition, Is there an option that I still can use TWRP to restore it properly?
~If the above is not possible is there a manual way to read out the made backup file using a program like 'Ext2Explore'(This crashes though when I open the file)
Or did I just completely screw up by checking the MD5 verification?
Once again kind regards
p.s. If the problem isn't clear tell me and and I'll try to explain it in a different way

You missed quote from post #4. ?
I believe that with a new device.... It should be a clean start. And I read post after post in different device sections of issues from restoring from other devices.
And so I never recommend it. It can, possibly, bring lots of issues.
But to each their own.
Good luck. ?

KJ said:
You missed quote from post #4. ?
I believe that with a new device.... It should be a clean start. And I read post after post in different device sections of issues from restoring from other devices.
And so I never recommend it. It can, possibly, bring lots of issues.
But to each their own.
Good luck. ?
Click to expand...
Click to collapse
Ohh right, sorry I completely read over your post my bad. But then again If I have to wipe the device wouldn't that totally remove the point of restoring the data partition ? or is the wipe command just for the system partition?

sambo940 said:
Ohh right, sorry I completely read over your post my bad. But then again If I have to wipe the device wouldn't that totally remove the point of restoring the data partition ? or is the wipe command just for the system partition?
Click to expand...
Click to collapse
What I'm getting at, is don't restore the data partition. You can try, but I often read of lots of issues doing it.
Yes, I implied wipe the device clean. Flash stock. Start fresh.
Now if you had a titanium backup of user apps on your pc... I'd say you'd have a much easier time restoring that to the new phone.
Just my 2 cents of course.

KJ said:
What I'm getting at, is don't restore the data partition. You can try, but I often read of lots of issues doing it.
Yes, I implied wipe the device clean. Flash stock. Start fresh.
Now if you had a titanium backup of user apps on your pc... I'd say you'd have a much easier time restoring that to the new phone.
Just my 2 cents of course.
Click to expand...
Click to collapse
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.

sambo940 said:
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
Click to expand...
Click to collapse
The pictures are gone. A nandroid doesn't back those up or anything on the internal sdcard
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
The pictures are gone. A nandroid doesn't back those up or anything on the internal sdcard
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well that certainly is a bummer, and also very misleading from the nexus toolkit. From now on I shall back-up my phone more properly and well stop using those darn toolkits,
Thank you for your time.

sambo940 said:
Well that certainly is a bummer, and also very misleading from the nexus toolkit. From now on I shall back-up my phone more properly and well stop using those darn toolkits,
Thank you for your time.
Click to expand...
Click to collapse
Did you make an adb backup in the tool kit? That would have your pics. But a flashable nandroid you flash in recovery would not.
Sent from my Nexus 5 using XDA Free mobile app

sambo940 said:
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
Click to expand...
Click to collapse
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.

jd1639 said:
Did you make an adb backup in the tool kit? That would have your pics. But a flashable nandroid you flash in recovery would not.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Nope, I did not. And the ignorant person that I am just assumed that the nandroid backup would back up everything since the toolkit says "Make full Backups"
So well I guess I just have to accept the fact that I lost those things
eddiehk6 said:
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
Click to expand...
Click to collapse
Not exactly what I was looking but I'll keep it in the back of my head in case something similar might happen in the future(lets hope not) Thanks.

Install Foldersync and set your sdcard to sync to a computer wirelessly
Sent from my Nexus 5 using Tapatalk

eddiehk6 said:
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
Click to expand...
Click to collapse
I am assuming that you used a tool like Android File Transfer.
So what I'm trying to do is the same thing, backup my entire old N5 32GB as I had also requested an RMA of the device. Is it accurate in stating that you want me to copy every folder that shows up on the AFT window (Note: I am using a MAC) and copy that onto a folder on my computer. Then copy over everything on the new device (bootloader unlocked, rooted, same TWRP version installed) and restore via the Nandroid backup from my old phone (which was also transferred as indicated above).

dcxgod said:
I am assuming that you used a tool like Android File Transfer.
So what I'm trying to do is the same thing, backup my entire old N5 32GB as I had also requested an RMA of the device. Is it accurate in stating that you want me to copy every folder that shows up on the AFT window (Note: I am using a MAC) and copy that onto a folder on my computer. Then copy over everything on the new device (bootloader unlocked, rooted, same TWRP version installed) and restore via the Nandroid backup from my old phone (which was also transferred as indicated above).
Click to expand...
Click to collapse
I didn't use AFT, just plugged straight into PC, sorry no experience with Mac
Basically both phones were connected, and I copied the whole "/sdcard" straight from one phone to another, without making an initial copy to the PC
You want to replicate the same file structure

Nexus 5 Stuck in Google logo screen

Hi guys,
Unfortunately my Nexus 5 kinda died on me today and I'm almost devastated. The phone froze and then restarted (I pressed the power button a couple of time, so I’m not sure if I restarted it or it did it by itself) and stayed stuck on the Google logo screen. I tried a couple of things but none works – booting it in recovery -> wipe partition cache; shutting it down and restarting it; leave it like that and praying to God…
I need your help. What can I do in order to fix this and keep my personal data on the phone – apps (with their data – I have a couple of journaling apps that are very important to me), messages, pictures, history, calls and so on…
The most important thing for me is to retrieve this data, so a factory reset is out of the question. Is there any way I can fix this? If not, how can I recover/retrieve all my data from the phone?
P.S. I'm using the latest Android OS, without that last OTA update, the booloader is unlocked and stock...

You could flash twrp, create a nandroid backup, copy the backup to your phone for safe keeping, restore the backup to an identical phone (you'll have to change the serial number of the backup to the phone that will be used for the restore), and hope it all works.
If you don't have access to an identical phone, you could try wiping the phone and restoring the backup.
You could flash twrp and copy off the important data.
Lastly, you could flash a stock rom, flash twrp, and restore your data and apps.

audit13 said:
You could flash twrp, create a nandroid backup, copy the backup to your phone for safe keeping, restore the backup to an identical phone (you'll have to change the serial number of the backup to the phone that will be used for the restore), and hope it all works.
If you don't have access to an identical phone, you could try wiping the phone and restoring the backup.
You could flash twrp and copy off the important data.
Lastly, you could flash a stock rom, flash twrp, and restore your data and apps.
Click to expand...
Click to collapse
Thank you for your kind and quick reply. I'm almost a complete android illiterate so I will bug you with a couple more questions, just for a better understanding.
So flashing TWRP means installing it...
1. Am I able to do this, considering the state of my phone? And will I be able to do the nandroid backup?
2. Is this tutorial good? http://www.xda-developers.com/how-to-install-twrp/
3. My phone is not rooted. Does this matter?
4. My phone has a capacity of 15 gb, of which approx. 1.5 gb were left free... Will I still be able to do the backup?
Thank you

The TWRP tutorial should be good - it's an XDA post...
You don't have to install TWRP, though it's a good idea unless you really don't want it. You can run it temporarily and on the next boot you'll be back to normal stock recovery. Booting temporarily will allow you to make a backup, but the risk is that you also back up the problem and then restoring the backup will also restore the problem - but it's worth a try.
"3. My phone is not rooted. Does this matter?" No, TWRP doesn't need root.
"4. My phone has a capacity of 15 gb, of which approx. 1.5 gb were left free... Will I still be able to do the backup?" Probably not - a backup is probably about 3GB, but if you manage to get as far as connecting to your PC and seeing your internal storage in Windows Explorer, you can copy the essential data (photos, etc.) to the PC and then do the backup and attempt the restore.
Press power & volume down simultaneously until you get to the bootloader screen with the green robot on its back. Connect the device to the PC - I'd recommend a direct laptop connection, not via a USB hub.
Start a CMD window and navigate to your PC adb/fastboot directory.
Type "fastboot devices" (no apostrophes) - if you're properly connected, you'll see something like "459uirgggg4 fastboot", which is your device id. A blank line means no connection.
To boot TWRP temporarily - "fastboot boot twrp.img".
To install TWRP permanently - "fastboot flash recovery twrp.img".
Once complete, use the volume keys to find "Reboot recovery". When you're in recovery, with any luck you may be able to see your internal storage in Windows Explorer, and you can at least retrieve your data. You could then try the restore, and if it doesn't work, a full installation of the latest ROM and rebuild your device from there (though Google automatically restores most of your apps if you had chosen that option).
Double-check these commands against other posts - I offer no guarantees, but at least a bit of hope...
Good luck.

Thank you! One more quick question, if I get as far as connecting and seeing my internal storage, would I be able to erase some data, in order to make room for the backup?

Yes, that's exactly what I meant. Photos are simple to identify, take up quite a lot of room, and can easily be transferred to your PC for safety and then deleted from the device. Anything free-standing (i.e. photos, for example, are independent of the app which captured them) and easily-identifiable, copy and delete from the device. Things like SMSs are trickier, since they may be held in not-obvious places or formats. If you take a copy to your PC, and delete to free space, you may have enough space for the backup, but as I mentioned you may just be backing up the problem as well as the system (backups don't tend to copy user data).

dahawthorne said:
Yes, that's exactly what I meant. Photos are simple to identify, take up quite a lot of room, and can easily be transferred to your PC for safety and then deleted from the device. Anything free-standing (i.e. photos, for example, are independent of the app which captured them) and easily-identifiable, copy and delete from the device. Things like SMSs are trickier, since they may be held in not-obvious places or formats. If you take a copy to your PC, and delete to free space, you may have enough space for the backup, but as I mentioned you may just be backing up the problem as well as the system (backups don't tend to copy user data).
Click to expand...
Click to collapse
Okay, here's the current situation - I managed to connect it to my pc and it's visible.
I saved my photos and cleared up some space. I now have 9 GB of available memory.
I tried TWRP (didn't install it though, as I receive an error, saying that it can't complete the command) and manage to boot it and enter the backup menu.
Unfortunately, it cannot backup my data, as it remains stuck on "updating partition details"...
Not sure what to do... Should I wait longer? It stayed like that for approx. 50 min, before I restarted it. Should I try a previous version of TWRP? Should I try a different program/method of doing a nandroid backup?
Also, there were options to backup my: system, cache, data, boot etc. Choosing to backup only my data would do the trick? As I said, I'm most concerned about my journaling apps, that were not backed up.
Anyways, here is something interesting that happened after I restarted it during the TWRP stuck backup process - the phone started and passed the google logo screen! And I managed to enter it. Things appeared to be normal and I was overwhelmed by hope. However, when I tried to open an app, it froze and started all over again. And one more detail, the battery was low, like 10%. It was low yesterday, too, when it died the first time. Could it be related? Do you guys make anything out of this? Should I proceed by backing up my data and flash a new OS?

Nice to see some progress...
The first thing to do is to get the battery properly charged. Some functions (I'm thinking specifically of encryption, which demands at least 50% charge plus the device plugged in) won't work properly on a low charge. It may not be the cause, but it certainly won't help if the battery is low.
9GB is now plenty to take an entire backup. The TWRP backup screen shows how much data is in each partition. I'm not entirely sure exactly what "data" does back up - I very much doubt (from experience) that it will back up things like photos, but as I said before some data is stored in obscure places and you may be lucky. Back up everything except cache - the defaults in 3.0.2.
Definitely back up EFS. Read around and see the havoc it causes if you have problems and don't have it backed up.
So... you temporarily booted into TWRP? Latest 3.0.2? And the "updating partition details" message was after you pressed the backup button? There shouldn't be any delay - my backups of 6GB on my N6 take only 5 minutes - the N5 is slower but not that much slower, and you have a lot less to back up. If TWRP still continues to be difficult, yes, try the previous version. Even back to a version 2 if necessary.
Try the backup when the device is charged, save it to your PC, and then reboot. Fingers crossed. Good luck.

dahawthorne said:
Nice to see some progress...
The first thing to do is to get the battery properly charged. Some functions (I'm thinking specifically of encryption, which demands at least 50% charge plus the device plugged in) won't work properly on a low charge. It may not be the cause, but it certainly won't help if the battery is low.
9GB is now plenty to take an entire backup. The TWRP backup screen shows how much data is in each partition. I'm not entirely sure exactly what "data" does back up - I very much doubt (from experience) that it will back up things like photos, but as I said before some data is stored in obscure places and you may be lucky. Back up everything except cache - the defaults in 3.0.2.
Definitely back up EFS. Read around and see the havoc it causes if you have problems and don't have it backed up.
So... you temporarily booted into TWRP? Latest 3.0.2? And the "updating partition details" message was after you pressed the backup button? There shouldn't be any delay - my backups of 6GB on my N6 take only 5 minutes - the N5 is slower but not that much slower, and you have a lot less to back up. If TWRP still continues to be difficult, yes, try the previous version. Even back to a version 2 if necessary.
Try the backup when the device is charged, save it to your PC, and then reboot. Fingers crossed. Good luck.
Click to expand...
Click to collapse
Dahawthorne, thank you! I managed to make a backup after following your suggestion regarding the battery.
However, I didn't do a factory reset... not yet. Something strange happened while I tinkering with it (basically starting it and shutting it down with a furry) - it entered the OS! And everything was there and seemed to be fine, I was able to access my apps and saved a couple of things. But... when I clicked on a web page, it froze again and I was back at square one. Could it be that I have too many tabs/web pages in the background?

If it's only Chrome (or other browser?) that's making it freeze, you might want to try installing a different browser.
In the meantime, given your situation, I'd concentrate on recovering all the data you want and copying it to your PC for safety in case you have to resort to a factory reset or full re-flash of the ROM.
In case you can't find the data for the reasons I originally mentioned, you could try the Play Store for backup applications - e.g. there's a good SMS backup app which will back up & restore your texts. There may be something similar for your journaling app.
(And what's a "furry"...? )

Various troubles with my OnePlus 7pro (rooted) + questions about restoring Nandroid

Dear community, I am facing several troubles with my OP7pro which I think can be quite easily handled but my knowledge is just too little.
I am running OOS 10.0.2 with Renovate ICE, rooted with Magisk and on TWRP 3.3.1-70 - stock kernel and normally encrypted. I am facing various troubles that started after upgrading from 9.5.13 tot Android 10. I do not know if they are directly related. I do have Nandroids, BUT the phone is my daily driver, also for work, and a factory reset will just take too much time.
What are the troubles you ask?
- I am not able to enter the menu Buttons&Gestures/navigation/set up navigation bar. The screen blinks and I am back in the upper menu. If I press this menu again I get a "Settings stopped". This sucks, because I want to set up my on-screen buttons
- I used to use Plus Beat in combination with RICE on Android 9. Worked perfect. Whatever I set up, Plus Beat just does not work. That sucks big time.
- I am not able to set on screen buttons to for example switch between recent apps or get anything else but horizontal recents (which is slow and to me sucks). QuickSwitch via Magisk doesn't bring anything.
NOW TO THE QUESTIONS:
I GUESS (! but am not sure!) that a factoryreset could and should solve these problems. I could and would do that, but, I need to be up and running and have my settings back quickly. Internal memory (root) I could copy to PC and paste back afterwords. But is there some way I could put my settings (in the menu) and all my apps (250+) back via Nandroid data?
I have the following things backed up in TWRP:
- Boot
- System Image
- Vendor Image
- Data
- Modem
- EFS
If I do a complete new factory set-up (for example via Maurefranio's tool), to refresh my system (I guess the failure is in there), can I put back other parts of the Nandroid to have all the rest back? Also in the menu-settings, color-setting etc. etc. etc.?
I know it sounds rooky, but I hope someone takes time to help me a little. I do use Titaninium etc. but I can't spend hours and hours on a recovery. In that case I'd probably decide to keep using the OP7pro as I do, but it's frustrating that RICE and Plus Beat don't work fully and some other errors. The usability to me is 4 out of 10 - where in Android 9 it was surely 9 out of 10.
Greetings,
existenz

Are you running a substratum theme? That could be the settings issue. But that's about all I could help with. Never restored anything using twrp on this phone. Most I've done is backup my apps with swift backup, factory reset, or MSM tool, and restore my apps.
How quickly do you need your phone up and running? You could backup with swift backup, factory reset and only restore what you need for now then do the rest when you have time.

@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!

exis_tenz said:
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
Click to expand...
Click to collapse
In that case, I would just use swift backup, backup to your device. Transfer SD card contents to your computer, factory reset. Transfer SD card files back. Swift backup can backup all apps and data. I believe that would work for what you want.
I, however, do not know what parts of the nandroid do what as I usually just don't bother with it.

GeekMcLeod: appreciate your advise, but Nandroid is there for a reason.
Is there anyone who can please help me what to do best? I mean, one of those Nandroid-partitions holds the clue, right?
I am also facing overnight Batterydrain of about 30% (from 80 to 50 in about 7-7,5 hours).

No Nandroid specialists in the house?

You need to wipe your data. Use Swift to backup apps, messages and call logs. Google will do it's best to restore settings upon setup. Your problem is almost guaranteed to be in data. If you need that data, I would recommend going back to whatever version of pie you were on before. Swift won't restore app permissions, as far as I know so be sure to double check if you restore apps with Swift.