I think I improperly handled my Titanium Backup restore to this phone. The messaging app keeps crashing and I'm seeing the following in the logs:
E/DatabaseUtils( 2920): android.database.sqlite.SQLiteException: no such table: wpm: , while compiling: DELETE FROM wpm WHERE thread_id = 9223372036854775807
I've cleared data for the Messaging app and rebooted, but I'm still seeing it. My guess is that the SMS/MMS storage isn't in the messaging app, but I'm not sure which other app I need to clear data to get this fixed.
Thanks for any help,
Craig
Clear messaging data (the way you did already), boot to recovery, and clear cache & dalvik cache.
Wiping dalvik cache has fixed issues with messaging for me in the past. I never experienced crashing after fresh installs though, only after swapping apks. It's worth a try though.
I cleared cache from recovery, but I don't have a dalvik cache clear option in recovery (I don't have CWM installed). Clearing cache had no affect. Other ideas? This is a bit frustrating... Even using a third party message application, I'm getting the Force Close dialogs for the Messaging app.
I think I'm going to need to clear dialer storage. Unfortunately, I'm not able to stop the dialer storage or clear the data. Other ideas on how to clean that out so that I can start fresh? (without having to do something crazy like a factory reset)
Thanks again,
Craig
csetera said:
I cleared cache from recovery, but I don't have a dalvik cache clear option in recovery (I don't have CWM installed). Clearing cache had no affect. Other ideas? This is a bit frustrating... Even using a third party message application, I'm getting the Force Close dialogs for the Messaging app.
Click to expand...
Click to collapse
Dalvik cache is in the advanced menu.
Sent from my Galaxy SII
Either I'm blind or I don't have an advanced menu.
Either way, I'm convinced that it won't help. My Titanium Backup was from Cyanogenmod (2.3.7) and the Galaxy S II is at 2.3.6. My assumption is that I've gone and restored SMS databases that are incompatible and I need to get rid of those before things will work. My current issue is that I can't stop Dialer Storage and I can't "Clear Data" for Dialer Storage, so I'm not sure what I can do next...
I'm considering coming at it from the command-line (adb) and deleting raw databases, but that seems pretty dangerous and I'm hoping someone can offer me a better approach.
csetera said:
Either I'm blind or I don't have an advanced menu.
Either way, I'm convinced that it won't help. My Titanium Backup was from Cyanogenmod (2.3.7) and the Galaxy S II is at 2.3.6. My assumption is that I've gone and restored SMS databases that are incompatible and I need to get rid of those before things will work. My current issue is that I can't stop Dialer Storage and I can't "Clear Data" for Dialer Storage, so I'm not sure what I can do next...
I'm considering coming at it from the command-line (adb) and deleting raw databases, but that seems pretty dangerous and I'm hoping someone can offer me a better approach.
Click to expand...
Click to collapse
Advanced menu in recovery.
....and ahh....so that's what it is. Never restore system data across roms! Only missing apps + data. Make a titanium backup (full backup - apps and system data). Do a full wipe and install your rom again; when you do your titanium restore, ONLY RESTORE MISSING APPS + DATA.
I don't have an advanced menu in recovery that I can see...
In the end, it doesn't matter, although I had to go a bit hardcore. I dropped to a shell and deleted the SMS storage databases:
Code:
[[email protected]] temp $ adb shell
$ su
# cd /data/data/com.android.providers.telephony/databases
# ls
shared_prefs
mmssms.db
telephony.db-wal
telephony.db
telephony.db-shm
nwk_info.db
mmssms.db-wal
mmssms.db-shm
# rm mmssms.db mmssms.db-wal mmssms.db-shm
Followed by a reboot and now messaging is working fine. With that said, is there any way to "export" the messages from my old device and import them into the new? I can survive without them if necessary, but it would be nice if I could keep them.
Answer my own question... This app worked perfectly to save off my old SMS and import them into my new phone... Life is good now.
https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
Learn from this experience haha.....
Good stuff.
Sent from my Galaxy SII
Indeed a quick and nice solution.
I think it's worth noting that this solution will effectively delete your SMS repositories. So handle with care.
Related
So I made a nand of the rom I'm using and flashed it to my wife's phone (so she wouldn't have to set her phone up at all). It logged in under my accounts (which I expected). I removed my FB account but it will not let me remove my gmail account. It says the only way I can do that is to factory reset the phone, which defeats the point.
Does anyone have the setup wizard app or know where I can find it? I couldn't find it in the market.
Am I fighting a lost cause here?
i beleive you are I personally have yet to figure out how to remove your gmail account you can add a gmail of hers but i dont think you can remove yours from it.
Nevermind. I gave up and did a clean install. I'll just use Titanium and install her settings back. No biggie. I was just being lazy.
I am curious though if that set up wizard app would let me remove a gmail account from a phone. I even logged in and syned with her gmail account and it wouldn't let me remove mine.
Really simple... flash a rom that doesn't come with google apps.
Hungry Man said:
Really simple... flash a rom that doesn't come with google apps.
Click to expand...
Click to collapse
What I'm aiming to do is put my backup on my wife's phone...only with the ability to replace my accounts and login with hers. So pretty much any nand I create is going to have google apps already flashed.
To install a nand restore on another phone
all you have to do is put it in the right folder.
Step 1) Make a nand Backup on the new phone.
Step 2) Take the nand backup from YOUR phone, save it somewhere
step 3) Save YOUR nand backup to the right folder inside hers.
For example: Her phone will look for
/sdcard/nandroid/HTC123ABCDEFG
so her backup will be /sdcard/nandroid/HTC123ABCDEFG/2010-0814-1234/ or something
your phone might be
/sdcard/nandroid/HTC456HIJKLMNO
so you need to take your backup, maybe called /2010-0821-1111/ and put it in her folder, so that on her SD card you have
/sdcard/nandroid/HTC123ABCDEFG/2010-0821-1111/
Then she can 'nand restore' that, perfectly.
I have done this when getting new Eris's. First root the new Eris.
Then make a nand backup (so it creates the right folder)
Then drag the old nand backup into that folder
The problem is that once you nand restore, whatever Google account was set up with that backup is the ONLY primary Google account that will be allowed for that phone. So your Contacts/Calendar/Gmail syncing will have to be done with that original Google account. You have to data/factory reset anyway to change it. You could go Settings >Accounts and sync> and uncheck the the boxes for syncing contacts, gmail, and calendar, but that might be impractical.
pkopalek said:
To install a nand restore on another phone
all you have to do is put it in the right folder.
Step 1) Make a nand Backup on the new phone.
Step 2) Take the nand backup from YOUR phone, save it somewhere
step 3) Save YOUR nand backup to the right folder inside hers.
For example: Her phone will look for
/sdcard/nandroid/HTC123ABCDEFG
so her backup will be /sdcard/nandroid/HTC123ABCDEFG/2010-0814-1234/ or something
your phone might be
/sdcard/nandroid/HTC456HIJKLMNO
so you need to take your backup, maybe called /2010-0821-1111/ and put it in her folder, so that on her SD card you have
/sdcard/nandroid/HTC123ABCDEFG/2010-0821-1111/
Then she can 'nand restore' that, perfectly.
I have done this when getting new Eris's. First root the new Eris.
Then make a nand backup (so it creates the right folder)
Then drag the old nand backup into that folder
The problem is that once you nand restore, whatever Google account was set up with that backup is the ONLY primary Google account that will be allowed for that phone. So your Contacts/Calendar/Gmail syncing will have to be done with that original Google account. You have to data/factory reset anyway to change it. You could go Settings >Accounts and sync> and uncheck the the boxes for syncing contacts, gmail, and calendar, but that might be impractical.
Click to expand...
Click to collapse
It took me a few tries to figure out that I had to put my nand in her file located at sd/nandroid/whateverfilename and couldn't simply drop my sd/nandroid/whateverfilename/datenandwascreated file on her phone.
Correct me if I'm wrong. Doing a factory reset would return the rom to a factory state (like a fresh wipe and flash of a new rom)? Surely google/verizon/htc thought that people might want to change their e-mail address for whatever reason and included a way to do this without resetting the phone? Guess not.
Sent from my ERIS using XDA App
pkopalek said:
The problem is that once you nand restore, whatever Google account was set up with that backup is the ONLY primary Google account that will be allowed for that phone. So your Contacts/Calendar/Gmail syncing will have to be done with that original Google account. You have to data/factory reset anyway to change it. You could go Settings >Accounts and sync> and uncheck the the boxes for syncing contacts, gmail, and calendar, but that might be impractical.
Click to expand...
Click to collapse
Last night I ran a quick experiment with a Froyo ROM (Kaos V30):
- Shut down phone
- booted Amon_RA
- # mount /data
- # rm /data/system/accounts.db
- # umount /data
- rebooted
Reboot seemed fine, and there were no (Gmail) contacts present in the dialer, nor any access to Gmail. Shortcuts to specific (phone) contacts were still in my home screens (including images of the person), but clicking on them resulted in an error. No apparent FCs anywhere.
Clicking on the Market app took me immediately to the Google Account setup screen (which I believe is the same thing as Settings -> Accounts & sync -> Add account -> Google). I don't know if this (behavior) is unique to 2.2 or not.
I don't have a second Google account, so I just re-entered the username/pass for my account - the same one that had already been on the phone, and the phone started "syncing". I sort of wondered what might happen (because I am using Froyo "Save my settings"), but everything came back as I would expect - Contacts, Gmail, etc.
I would have proceeded a little further with this experiment, but I couldn't access the Market ("connection error") (about 1am EST Saturday morning), so I stopped, assuming this was a failure - and restored a Nandroid backup. When the restored ROM also had trouble with the Market, I thought - "oh, boy, what have I done?" But, it seems that a number of people have reported trouble with the Android Market late last night / early this AM - and the Market was working this AM on my restored ROM, too.
I could repeat the experiment if there is any interest, and this time use my GF's account for testing purposes. There are probably some things cached that should be cleaned up prior to adding back in a Google account; probably it wouldn't hurt to use
Settings -> Applications -> Manage applications
To clear the data and cache areas for a few things such as
Browser
Calendar
Calendar Storage
Contacts
Contacts Storage
Dialer
Dialer Storage
Email
Gmail
Google Voice
Maps
Market
(Plus others as appropriate - Twitter, FB, etc)
bftb0
bftb0 said:
Last night I ran a quick experiment with a Froyo ROM (Kaos V30):
- Shut down phone
- booted Amon_RA
- # mount /data
- # rm /data/system/accounts.db
- # umount /data
- rebooted
Reboot seemed fine, and there were no (Gmail) contacts present in the dialer, nor any access to Gmail. Shortcuts to specific (phone) contacts were still in my home screens (including images of the person), but clicking on them resulted in an error. No apparent FCs anywhere.
Clicking on the Market app took me immediately to the Google Account setup screen (which I believe is the same thing as Settings -> Accounts & sync -> Add account -> Google). I don't know if this (behavior) is unique to 2.2 or not.
I don't have a second Google account, so I just re-entered the username/pass for my account - the same one that had already been on the phone, and the phone started "syncing". I sort of wondered what might happen (because I am using Froyo "Save my settings"), but everything came back as I would expect - Contacts, Gmail, etc.
I would have proceeded a little further with this experiment, but I couldn't access the Market ("connection error") (about 1am EST Saturday morning), so I stopped, assuming this was a failure - and restored a Nandroid backup. When the restored ROM also had trouble with the Market, I thought - "oh, boy, what have I done?" But, it seems that a number of people have reported trouble with the Android Market late last night / early this AM - and the Market was working this AM on my restored ROM, too.
I could repeat the experiment if there is any interest, and this time use my GF's account for testing purposes. There are probably some things cached that should be cleaned up prior to adding back in a Google account; probably it wouldn't hurt to use
Settings -> Applications -> Manage applications
To clear the data and cache areas for a few things such as
Browser
Calendar
Calendar Storage
Contacts
Contacts Storage
Dialer
Dialer Storage
Email
Gmail
Google Voice
Maps
Market
(Plus others as appropriate - Twitter, FB, etc)
bftb0
Click to expand...
Click to collapse
THAT'S AWESOME! I would be very interested for you to repeat this experiment. This would be VERY useful for me. My wife likes the whole rooted phone with all the extra options but she's not into it like I am. If this works and is stable, I could easily set her phone up exactly like mine. I would test it myself but I'm not an advanced adb user. If I break something, it's just broke which would probably equal the doghouse for me since it's my wifes phone.
If this works, you should write a how-to for the community. I couldn't find one when I searched and I'm sure others would find it useful.
Sent from my Froyo Eris using XDA App
joshw0000 said:
THAT'S AWESOME! I would be very interested for you to repeat this experiment. This would be VERY useful for me. My wife likes the whole rooted phone with all the extra options but she's not into it like I am. If this works and is stable, I could easily set her phone up exactly like mine. I would test it myself but I'm not an advanced adb user. If I break something, it's just broke which would probably equal the doghouse for me since it's my wifes phone.
If this works, you should write a how-to for the community. I couldn't find one when I searched and I'm sure others would find it useful.
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
So long as you have adb working, you do not need to be an "advanced" adb user in order to help out with the testing. After you create a Nandroid Backup in Amon_RA, there are literally only four lines you type in using the "adb shell" (with Amon_RA still running):
Code:
mount /data
rm /data/system/accounts.db
umount /data
exit
... and then do a Wipe Dalvik-cache in Amon_RA
Everything else that I suggested is performed using
Settings -> Manage -> Manage applications
in the main OS. (I suppose it might even be possible to delete /data/system/accounts.db using a root-aware file manager, but I prefer to do stuff like that in an offline fashion)
If something goes wrong - well, you have a full Nandroid backup available to restore to. The same thing goes for your wife's phone too, right?
bftb0
PS For anyone else reading this thread: it is a quarter-baked idea (not even half-baked); don't take away from this any sort of mis-impression that this has undergone any significant testing (none at all on 2.1, in fact). Feel free to experiment yourself - but make good Nandroid backups!
bftb0 said:
So long as you have adb working, you do not need to be an "advanced" adb user in order to help out with the testing. After you create a Nandroid Backup in Amon_RA, there are literally only four lines you type in using the "adb shell" (with Amon_RA still running):
Code:
mount /data
rm /data/system/accounts.db
umount /data
exit
... and then do a Wipe Dalvik-cache in Amon_RA
Everything else that I suggested is performed using
Settings -> Manage -> Manage applications
in the main OS. (I suppose it might even be possible to delete /data/system/accounts.db using a root-aware file manager, but I prefer to do stuff like that in an offline fashion)
If something goes wrong - well, you have a full Nandroid backup available to restore to. The same thing goes for your wife's phone too, right?
bftb0
PS For anyone else reading this thread: it is a quarter-baked idea (not even half-baked); don't take away from this any sort of mis-impression that this has undergone any significant testing (none at all on 2.1, in fact). Feel free to experiment yourself - but make good Nandroid backups!
Click to expand...
Click to collapse
I do have a working adb and understand for the most part that you're deleting accounts.db in /data/system?? What I'm not following is why I would need to boot into recovery to delete the file. Would the process not work the same if you made the changes while booted in the rom? Do the changes affect the recovery partition at all or did you boot to recovery so you can immediately wipe dalvik and reboot? That's my biggest fear.
Sorta the same question - does it matter where you're booted when you do adb commands (booted, usb mounted, recovery, powered off)?
P.S. I've read several responses you've posted in other threads. You're very thorough in reponses and I personally have learned a lot from reading them. Thanx for your input and help with us noob and novice users.
Sent from my Froyo Eris using XDA App
joshw0000 said:
I do have a working adb and understand for the most part that you're deleting accounts.db in /data/system?? What I'm not following is why I would need to boot into recovery to delete the file. Would the process not work the same if you made the changes while booted in the rom? Do the changes affect the recovery partition at all or did you boot to recovery so you can immediately wipe dalvik and reboot? That's my biggest fear.
Sorta the same question - does it matter where you're booted when you do adb commands (booted, usb mounted, recovery, powered off)?
Click to expand...
Click to collapse
The changes do not affect the recovery partition - the reason that the recovery partition is used for almost all administration involving system elements is because there are not files which are "locked" by applications that are using those files, nor do you have anything running which depends on that file at the moment it is deleted.
The account credentials are important to lots of applications which are running on the phone in the regular OS, and you will get strange behaviors, crashes, and possible corruption of application state if you just yank the file out from underneath all those applications. You could try to stop those apps first - but a lot of them auto-restart on their own.
I'll use an analogy; it's like the difference between setting a table without a tablecloth, versus trying to remove the tablecloth after all the dishes are in place.
There are lots of reasons to prefer doing things in an offline mode, but the primary one is that you are not "yanking X out from underneath Y" - when "Y" thinks that "X" is still there.
It is typical for both system and application logic to do things like check for files on startup, and then either rebuild them from defaults if they are not present, or read/write their contents if they are already present. It is a lot more rare for applications to be coded in way that they are constantly check to see if something they though was there has suddenly disappeared. Moreover, the way that locking works with Linux kernels, you can delete a file that is opened by another process, and replace it with a new file - but the processes that are still running with that file open will still have a copy of it.
As for being scared - you have a Nandroid backup, right?
bftb0
That makes a lot since. I'll try this method out the next time I change my wife's rom.
Sent from my Froyo Eris using XDA App
Is there a kind of system maintenance routine necessary (or beneficial) to keep Android running in top condition? I've seen that permissions can be repaired via CWMod and Dalvik cache, etc, but what else should we do to maintain the system performance and stability, etc.?
well, idk if this helps, but tmobile told me to clear the user data every 2 months or so...
User data holds what?
I'm not sure I trust the "expertise" of a T-Mobile rep, but thanks for the response.
I've had one instance where the system told me that my DB data was getting too full and asked me to purge it manually. I removed some stuff and then I noticed that the DB data went down in Titanium Backup, but I don't know what that does either, or how to keep it cleaned out.
If you are plain stock not rooted, delete cache data as the previous poster said. There is not an specific amount of time for this, but if you feel your phone starts too lag more than usual
If you are rooted, and have CWM installed wipe cache partition, and in Advanced do Wipe Dalvik cache, nad if you want wipe battery stats (Do this when your battery is full once in a while so yo get better battery reads)
I need to clear out the directories for apps from my internal SD card periodically. As I install and uninstall apps I get a bunch of directories on there that I don't need. I also like to reboot every few days to a week when my phone gets laggy.
To me, I should be able to Factory Reset my phone any time and get what was "Delivery" By Sprint/HTC/CustomROMChef
But I should be able to update (from market) any Market App.
So I see a lot of folks put a bunch of stuff normally in System/App in Data/App
So that users can uninstall it. That's fine.
But if users want it and factory reset (or clear data) it's completely gone and the only way to get it back is to flash.
If a Market App is in System/App and it be still updated from the Market.
If it can be updated from Market why can't it be uninstaled?
It seems there should be a script that runs when you clear data that repopulates Data to the same state it was delivered. But that would waste from ROM space.
What am I missing.
I hope folks follow my thinking and can straighten me out.
Thanks
Googling around I did find this one critical tidbit
Market updates with /system apps that aren't "supposed" to be in /system is a pain. The market will install an app into the /data/app directory by default, so if you have something like LauncherPro that is a non-system app by Google's definitions, but it's in your /system/app directory because it came pre-packaged with your ROM, then if you update from the market you end up with two copies of it -- a deprecated version in /system and the current version in /data.
You also lose any theming when you update from the market, but that's nothing new and iirc that's true for any themed app regardless of whether it's in /data or /system
Click to expand...
Click to collapse
In the world of s-off you don't factory reset anymore you wipe and reflash.
If you factory reset any apps or data in the /data will disappear.
The system directory is typically write protected unless you can get root permissions, any updates are stored in data. Devs will typically put the updated apps in the system dir saves some space, once an update comes out the space you saved is then lost.
Sent from my PG86100 using Tapatalk
Chuki82 said:
In the world of s-off you don't factory reset anymore you wipe and reflash.
If you factory reset any apps or data in the /data will disappear.
The system directory is typically write protected unless you can get root permissions, any updates are stored in data. Devs will typically put the updated apps in the system dir saves some space, once an update comes out the space you saved is then lost.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I understand what you are saying. But I'd like the option/concept of being able to clear Data without Reflashing.
So are you saying if a Market App (e.g. Google Maps) is in System and you update it from Market, it will always put the updated version in Data and leave the System one dormant (it will never replace or remove the one in system regardless of root status)?
How does Sprints Stock ROM do it? They allow removing some bloatware and I assume if I factory Reset, nothing would be missing, even if I uninstalled it.
All I can think they do is they bury a backup of Data in the ROM that is restored on Factory Reset.
Yes on the updated apps thing. Updates are saved to data the original is left dormant in system.
The apps in the stock rom are in system, certain ones can be removed or so you think. They are more like disabled, something allows to go dormant as you called it and the only way I know to get it back is a reset.
If certain rom devs move apps to data to be actually removed and you do a reset you lose those apps. If you don't want that to happen, I suggest backing up any and all apps you want sprint, HTC, other. Then reset and restore.
I have backups of all the stock Apps I like to use and if the rom includes it, and great! If not I have a good copy on hand.
Sent from my PG86100 using Tapatalk
Y factory reset when you could wipe dalvik and cache???,,, also learn how to move apps you want manually,,makes life easier for you sometimes
Sent from my PG86100 using Tapatalk
ktrotter11 said:
Y factory reset when you could wipe dalvik and cache???,,, also learn how to move apps you want manually,,makes life easier for you sometimes
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Because if you having problems, due to what ever reason, clearing cache is not always the solution.
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Flash a clean ROM, wipe cache and dalvik, do a factory reset and start from scratch.
Multiple fc can be caused due to several reasons like:
-wrong phone.apk
-wrong framework
-wrong ROM
-too much undervolt
Sorry for telling but my first sentence might be your fastest approach.
Tapatalked from my Samsung GT9100
Tyrol said:
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Click to expand...
Click to collapse
Try the following:
-Download this: Ultimate kernel cleaning script
-Reboot to CWM recovery
-Flash Ultimate kernel cleaning script
-Under kernel specific option, Reset extweaks settings
-format /system (under Mount and storage)
-Flash ROM (RR 2.61)
-Flash Gapps
-wipe cache partion
-wipe dalvik cache (under advanced)
-fix permissions (under advanced)
-Reboot your phone
My above steps will not wipe your and should definitely fix your problem
good luck
Thank you both for your suggestions!
Unfortunately, I didn't get to try them but I'll definitely be checking this again if (touch wood) this happens again. Hopefully it'll be useful to someone else facing similar issues, I know I couldn't find clear answers on what to do.
@jokesy If the /data partition is somehow stuck at read-only, I'm not sure formatting /system will help. I could be wrong, I apologise if I sound ungrateful ('cause I do appreciate your help) but wouldn't reflashing a ROM kind of overwrite the existing /system files already?
I'm not aware of the details and technicalities of what exactly happens during a ROM flash but according to the AROMA installer, it seems like /system is wiped first.
What I did
Gave up on backing up apps & WhatsApp through the normal ways, most of my TB apps are backed up daily anyway, just lost some data like that for Sleepbot.
Pulled WhatsApp database files from /data/data/com.whatsapp via ADB, restored the previous day's Nandroid backup & copied the database files to the relevant directory. I guess it may seem minor, but as everything was melting down on my phone, I kept getting messages from friends about project work in school & other stuff that I couldn't read so I really wanted to not lose all the new messages that had come in.
Restoring my Nandroid (thank God I backup daily) fixed everything, fortunately, but there are little quirks I'm still ironing out. Eg. My Godville app can't seem to connect to the main server & retrieve details of my character despite clearing data, uninstalling & reinstalling. Not too sure why.. :/
-----------------------
サンソングガラクシS II からタパトクで書いた。
@Tyrol
Ididn't know you were using aroma installer though, but formatting /system has nothing to ago with /data sms vice versa
Following my wouldn't have hurt though, ur would only ensure a clean system partition before install.
I'm happy for you
Better luck next time
Swyped from my Samsung Galaxy SII
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Karl.morteo said:
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Click to expand...
Click to collapse
Tough luck man. I don't know why the data corrupts spontaneously, it happened once to me when I was playing Plague, everything started FC-ing all of a sudden while I was in-game. Bizarre. Didn't want to do a full wipe so I just restored the /data partition from my latest Nandroid.
-----------------------
サンソングガラクシS II からタパトクで書いた。
I'm going to be ROM-ing for the first time (well, other than Safestrapping the Bionic for a day or two) and want to make sure I have the right thought in terms of running and upgrading a ROM over the long term. If I'm moving to AndroWook as my daily driver, I want to make sure I have a good procedure in place for quickly and easily upgrading to the latest version of the ROM.
The following is my understanding of this whole process. Is this procedure correct? My main concern is making sure I am doing everything right to be able to quickly update to the latest version of the ROM when it comes out, not spend a day re-configuring. Is there anything I am missing?
BACKGROUND: Partitions
Main Partitions Involved With Wiping
/system = Where the OS lives, along with the apps that are preinstalled
/data = Where user installed programs & their associated data/settings live. This data/settings is the part that gets deleted when you go Settings -> Applications -> pick an application and click "Clear Data". This is what Titanium Backup backs up for user apps (both the "apps" and "data" backed up live here). Also has SMS, contacts, settings, etc... the "system data" in TiBu
/cache = Cache files that help programs to load quickly. Harmless to wipe, as it will regenerate.
/sdcard = Internal sd card area where you keep files and use file manager. some programs also put files here. Not usually wiped.
external sdcard = Physical external sd card, if applicable. Not usually wiped.
Other partitions
/boot = Kernel and ramdisk. Don't wipe unless you fix it before rebooting.
/recovery = Where the recovery (stock or custom) lives.
/misc = Other settings not normally touched.
BACKGROUND: Types of Wiping
Cache = harmless. Cache regenerates itself over time to speed up phone.
Dalvik = harmless. This is simply another cache, this one having to do with Java.
Factory Reset = wipe /data and /cache. internal and external sdcard is NOT wiped
Wipe system = wipes /system (where the os and its preinstalled apps live)
Format data = wipes /sdcard (the internal sdcard)
Format external sd = wipes external sd card
ASSUMPTIONS & NOTES
You are rooted
You have Titanium Backup (TiBu)
For multi-user environment, modify the instructions to account for the need to backup/restore with TiBu for each user. Backup for each user, flash, then restore for each user.
BACKING UP
1. TiBu: Batch Backup all user apps & data (everything) in current ROM
2. TiBu: Batch verify the backup
3. Make a sketch of how your widgets/homescreen is supposed to look
4. If you are doing a total deep clean that wipes sdcard (generally not), here is where we want to back up anything else (sdcard files, etc)
5. File Manager: Backup apk for both TiBu & TiBu Pro to SD card
Alternate: Do nothing now, and we use market in new ROM later6. Download ROM & put on SD
WIPING & FLASHING
This part subject to change based on ROM maker's recommendations
1. Boot into recovery
2. Wipe and flash:
Option A: Clean flash (typically done, does NOT wipe sdcard):
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. For a total deep clean (not usually done, DOES wipe sdcard): Wipe system; Format data
5. Flash zip
Option B: Dirty Flash (usually only OK for minor updates):
1. Wipe cache
2. Wipe dalvik
3. Flash zip
4. There is no need to set up the ROM again in this case.
SETTING UP NEW ROM
1. Boot into new ROM
It will take 30-60 minutes to get up to full speed. After that time, it will be full speed after a reboot.
You can tell it to keep backed up to Google (backups up TO Google), but tell it NOT to restore from Google right now (restores FROM Google right now).
2. System > Applications > Unknown Sources
Restore TiBu & TiBu Pro from apk backup
Alternate: get from market
3. TiBu: Batch Restore system data - ONLY THE GREEN ITEMS
Do not restore red items
Do not restore user stuff yet. We are doing system stuff first.
Note that icons will not show correctly yet... nothing to be concerned about.
If the new ROM is vastly different, take care to restore only what is necessary.
4. Reboot
5. TiBu: Batch Restore missing apps with data - ONLY THE WHITE ITEMS
6. Click Market Doctor to verify that everything is hooked back up to the Market OK
7. Fix up homescreen - widgets & wallpaper
One by one, delete empty Widget then add new one.
Also choose the wallpaper you want
8. Check:
Date & time, alarms, ringtone, voicemail number, other settings
Anti-theft is operating properly
9. Market Place > My apps > Update any other apps
10. If over the course of time you find any apps giving problems, use the market to uninstall them and reinstall them to clear out any problems it may have had in restoring from TiBu
I just glanced thru that and this is what I saw quickly.
Option A: clean flash..... I always wipe system as well. This is not a big deal if you don't do it because I format the system in the installer in case people have forgotten.
I also delete cache and dalvik in the installer also in case people forget but I still end up doing them on the wipe page.
The only one really you need to use for a major version update is factory reset. This is just on my rom tho.. I can't speak for how others do it so always best to do the manual wipes also.
Tibu : It is never advised to restore system apps. Even between minor updates in case I have changed a system app.
If there is one that you really need restored then try restoring just the data for that one app and test it properly.
In the installer I do not write all apps to system anyway. There is very little in there that would take more than a few seconds to set back up.