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?
Related
Hey Guys, I'm a little bit of a noob here. I have had my captivate for about 6 months now and I started to get a little frustrated with the way the Captivate was set up compared to my old HTC Hero. I didn't have to root the Hero and could do anything with it I wanted. With the captivate it was another story. I rooted the new Captivate and it has been a wild ride. I follow the forums to see what is available after having Super User installed. I have to say I went a little crazy into the exploration of what i can and cant do. I learned what I cant do the hard way and spent almost 3 day's having problems with odin3 one touch flasher. Once i got everything back running to factory settings I decided to just set up the phone the way I like it and updated the config. for example I added the root access and updated the settings.db file to allow 3rd party apk installs. I than also deleted the wealth of useless crap At&T Preloaded onto the OS such as the apps and the 20 AT&T contacts. Fortunately now my phone and layout is exactly to where I want it. Unfortunately now I am afraid to perform other root mods on the phone and have to re flash the original factory settings on it and have to set it up all over again. I am not much of a programmer but do know end user support very well and was hoping that there would be a way to create a backup of the root directory so that in case I brick my phone (happend twice when I tried to replace the launcher program) I can just flash my backup so that I don't have to install apps, configure settings, and adjust the layout all over again? I was thinking of creating an update.zip would do it that i could keep on my sd card and flash it from recovery.
Can Somebody please Help!!!
Thanks,
Jay
Generally speaking, unless you use the same ROM, it is a bad idea to restore system settings.
Check out Titanium Backup from the Market. It works really well at backing up apps, data, and system data. Be sure to get the donate version so you don't have to manually install every single app (huge time/effort saver). It won't give you an update.zip file, but if you reinstall it and point it at it's backup folder, it can restore all of your data with minimal effort.
If you are prone to bricking your phone, back it up to an external SD card by entering "/<external sd>/Titanium Backup" as the backup path, replacing <external sd> with the real path (it's different on 2.1 and 2.2 ROMs).
Good luck.
Thanks, I actually already have Titanium Backup lite and i backed it up using the batch Backup all user apps + System Data but have no idea how to restore these backups if my phone bricks. I dont necessarily want to flash the phone to try it out. Any chance you know of where i can find out a little bit more information on how to restore backups with this app?
I also have the ClockworkMod Recovery where i have backed up my phone to an SD card. It says during the process Backing up system, data, datadata and than generates an md5sum. After this the phone boots back up and I was wondering if recovering using ClockworkMod is the same as flashing an update.zip rom but instead of using the stock version? Also this app seems a lot easier to use at there is an option to reboot into recovery and select roms
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.
My understanding of backing up a nandroid is that it creates an exact backup of your phone, as is, which can then easily be restored.
As advised, I have been trying out a couple of different ROMs to see which is best for me and with the advice of many of you, Ive mostly figured that process out.
But where I am struggling is figuring out how to optimize my use of Nandroids to streamline this. Heres the specific issue:
I flashed a ROM and then set everything up. I created my desktop screens, shortcuts to key contacts and apps, widgets, etc. Loaded pictures into my photo app, labeled favorites...usual stuff.
I then created a backup.
When I went to restore this backup, I ran into a bunch of issues. For example, the contact shortcuts were still in my launcher (Apex), but if I click on them they either pull up an incorrect contact or say "no such contact exists". So in the end, I need to go through and create all of these shortcuts again from scratch. Similar experience when I open the photo app (JustPictures) where all of the favorite labeled pictures are now gone. Other examples include apps that were on the device, but now no longer appear.
None of this is hard to fix, but it is very time consuming and makes it hard to use backup/recovery as a way to seamlessly flash and move between configured ROMs.
Am I doing something wrong? Any advice on how to optimize this so I can make this process manageable and not a barrier to trying something new but easily reverting when necessary?
You must he doing something wrong. I have never had any issues restoring a backup. And have never seen anyone else post about such things. You need to explain every step you took. It literally should be as simple as rebooting into recovery, clicking "Backup", let it do its thing, flash some other ROM, go play around with it, dislike it, refrain from posting in the ROM thread something like "tried out this ROM but didn't like it so I'm restoring a backup," reboot back into recovery, select "Restore", choose your backup, let it do its thing, and BOOM, back to the way it was.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
If you're not "wiping clean" system,data,cache , before restoring backups , do it ... or you'll face the problems you mentioned ... Actually you should never install or restore anything without formatting all those 3 areas..
Use also a good recovery , sk8witski 14.6 latest one ...
mahanddeem said:
If you're not "wiping clean" system,data,cache , before restoring backups , do it ... or you'll face the problems you mentioned ... Actually you should never install or restore anything without formatting all those 3 areas..
Use also a good recovery , sk8witski 14.6 latest one ...
Click to expand...
Click to collapse
Thanks! I went back and tried re-doing this step and it helped.
A related question: I use Apex Launcher and have a desktop customized with shortcuts to most used apps and contacts.
When I am flashing a NEW ROM (not restoring) - what is the best way to restore the desktop and shortcuts without having to manually redo it for each new ROM I try? This is definitely the biggest barrier for me in testing new ROMs as it takes a lot of work to redo each time and, without redoing it, its hard to simulate the same usage and experience when I move to something new.
If I just restore Apex with Titanium after flashing, often all the links/shortcuts/widgets are broken and need to be redone. Is there an order with which I need to reload/restore things? Is there a better way to backup and restore Apex settings so that they will come back and properly link to the underlying contacts and apps on a new ROM?
Thoughts?
Isn't there an option within the Apex settings to save your current configuration, or backup data, or something like that? Check there and try that.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Yes now I see that. I had been backing up via Titanium and restoring Apex using "restore App + Data".
I will play around with those, see what works or doesnt and report back in case its helpful to others.
Thanks.
[Pls excuse the minor x-posting; it's kind of urgent...]
After a full system/user/data backup of my rooted, stock otherwise, nexus with Titanium Backup Pro, decided to free some space by integrating updates into ROM.
Titanium Backup Pro got stuck in the middle of integrating "Google Now", which I had not even enabled, at about 36%; most parts of the UI froze and a reboot was required.
After that, got stuck in "Android is Upgrading - starting apps" for a very long time. After some more reboots, which got me stuck in the android animation indefinitely, TW recovery was called for, and after wiping cache & dalvik and a restore of boot & system partitions I'm back & stuck to "Android is Upgrading - starting apps"... and trying very hard not to restore data, 'cause I'll lose a ton of changes not backed up in TW (only in Titanium - that was going to be the next step). Feels like I'm being stuck in Android animation again for a vey long time and ADB shell regards the device unauthorized...
Any ideas/help quickly, greatly appreciated...
Thanks in advance,
-s.
I would expect unfortunately that something in /data will be screwed up too, if it failed transferring from there to /system
Bite the bullet and full nandroid restore followed by titanium restore. Always backup via nandroid immediately before any /system level changes.
Thanks for the swift reply...
Was going to do exactly that next, but wanted to have a tidy TW backup, with everything in it's right place beforehand. Had used the specific integration feature in the past with no problems whatsoever.
The problem is, last Titanium backup wasn't moved from nexus insides before getting stuck... So my best option and what I'm left with is the full TW backup from a Wednesday... Will restore now and report back [oh, sweet lord, being the wife's phone caretaker ]
-s.
Yeap.
Got the device back, _exactly_ how it was on Wednesday... Splendidly working, lost the hell of changes made afterwords, when handed over the device to my wife - and all of her customizations ever-since... and to think that all these happened because her own samsung got stolen on that day!
Shouldn't have tried to accomplish everything perfectly, in order and at once, if there must be a small piece of extracted knowledge from the incident... and that sh*#t happens!
Thanks everybody.
sdam said:
The problem is, last Titanium backup wasn't moved from nexus insides before getting stuck.
Click to expand...
Click to collapse
Not following you there...
Oops! Pls excuse my ignorance... being kind of an old-dog, thought that Titanium would be back to when I captured that last nandroid bckup, unless I manually moved the backup files in another device.
Happily restoring now all missing apps+system data & will see how it ends up...
But how?... thought that a full nandroid restore would do exactly that, in every aspect [noticed, also, TW reporting that restored /data without wiping media -folder? -mount? -smthng?, but didn't give any particular attention ]
Will report back.
Custom recovery doesn't backup or wipe /data/media/0 (/sdcard)
Sent from my Nexus 5 using Tapatalk
I stand merrily corrected.
I knew it doesn't backup /sdcard, but thought that that was because of issues of space and the fact that sdcards are supposedly 'removable' (not on Nexus, of course; my -well, wife's anymore- Meenova awaits to finish everything else in order to deal with it, which is exactly the next step), so I thought that they just followed the convention by not backing it up - but also thought that /sdcard was just a link to some folder or mount point and would thus get wiped during the restore, if you follow my old school thinking...
All's Well That Ends Well, like the bard wrote, I'm grateful to the miracles of this brave new world and we lived happily ever after -my wife and I, that is!
Space would be an issue. Once /sdcard was over half full, there would be no room to back it up.
On our n5, /sdcard is actually /data/media/0
Stock recovery wipes this (for a complete wipe) but custom recovery doesn't because it knows you'll want stuff on there as a flashaholic
Sent from my Nexus 5 using Tapatalk
Tired but happy, thanks again, for all the help & explanations.
Going to bed now, here being half past three in the morning -but wife is working Sunday's shift 2morrow in the 'paper and would have wanted her phone working...
Cheers,
-s.
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"...? )