My best bud was complaining about how slow his stock SGS was so I decided to help as I've fixed about 20 phones now without any issues! Until now!
Problem
Lost Contacts which were stored to phone memory
Lost memos
Almost all programs are Force Closing
History
Installed clockwork recovery as per Cyanogen Wiki page (http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide)
Then using the new SpeedMod kernel by Hardcore, I rooted the phone and also converted the file system to EXT4 to ensure the lagfix worked nicely
The Recovery automaticalled generated a Nandroid back-up before the file system conversion took place.
When phone started, a lot of programs Force Closed, so we ran a Fix Permissions and this solved most problems. However, a few days have passed and now the phone is constantly FC. The loss of contacts and memo's was annoying but he wasn't too bothered as had various back-ups
So I tried a Nandroid restore which works apart from system.img which it cannot find.
I wonder if the system.img backup doesn't work since the file system was changed to EXT4? Do you think if I push the nandroid backup using ADB, it will successfully restore the phone with contacts and memo's too?
That's why I never touch someone else's phone. Always something goes wrong that never gone on my phone.
Sounds like you need to do...
Wipe data/factory reset
Wipe cache partition
...in clockworkmod to make a clean install.
If your friend didn't set up a syncronisation in "Accounts and sync" between google and the phone, AFAIK you cannot revert back contacts and memos
After turning the file system to EXT4, it removes backups.Because its not a nandroid backup. Just backing up your files before the partition formatting. So, no luck.
I'm not a android expert, so I might be wrong about it.
Related
Hey guys,
Wondering if you'll be able to help me here.
I was running Cyan's 4.0.4 stable ROM, I made a Nandroid backup because I wanted to try out the 4.1.11.1. Anyway, I loaded up the new ROM and ran the fix_permissions script hoping that it would solve the force closes issues I was having. But, it didn't.
So I went to restore my Nandroid backup. It seemed to work, but then upon booting - all I got was a black screen and the top notification bar. It would not load the home screen and I couldn't access any apps!
I wiped and installed a clean 4.0.4 and it booted fine....but I'm just wondering if there's any way I can get my data back now.
Thanks for your help!
Casey Rain said:
Hey guys,
Wondering if you'll be able to help me here.
Click to expand...
Click to collapse
Wrong place to be asking....there is a Q&A forum.
You're gonna be told this is in the wrong section by someone sooner or later but in the meantime.......
Before you installed CM 4.11.1 had you done a wipe of your phone? Not just the normal wipe, the Ext3 wipe too. If not then it's likely that caused your black screen and problems. Trying to restore the nandroid backup without wiping up what was left over from that will have given you the force closes and other problems.
You've reinstalled 4.0.4 so you know it works so you can wipe again, wipe the Ext3 files (lose programs but they'll be back with nandroid mostly) and then restore your nandroid backup. It should work from there.
My apologies for not posting this in the correct section.
Thanks Dyonas, I will try that. How do I go about wiping the EXT partition?
I didn't wipe before installing the 4.1.11.1 - I used this script, having been led to believe that that would fix any problems. 4.1.11.1 booted fine but I was getting a lot of force closes even after running the script.
That's when I tried to roll back to 4.0.4 using the Nandroid backup, which appeared to work - but only brought up a black screen, and the notification bar.
You ran fix_permissions after loading the update and letting it boot and not before right?
Im just double checking as they maybe the issue. Still the only hope is your nandroid backup.
I would use the Amon RA recovery that allows for wiping ext3 and restoring your nandroid backup.
The script for fixing permissions would solve some problems but the main ones I think you experienced were because of changing from 4.0.4 (Cupcake), to 4.11.1 (Donut) and the changes involved. You can use the new recovery image to wipe ext3 from http://forum.xda-developers.com/showthread.php?t=566669 which is pretty self explanatory after it's installed.
Alternatively you can use Cyanogen's recovery and.......
console
mount /system/sd
rm -rf app
rm -rf app-private
rm -rf app_s
rm -rf dalvik-cache
recovery (to go back to recovery console)
wipe, just to be safe, then try restoring your nandroid backup or flashing 4.11.1 which shouldn't have as many issues after a full wipe.
Tried wiping the EXT from the AMON_RA recovery, then wiping, then restoring the Nandroid backup. Still the same problem with the black screen and not loading the launcher.
What's strange is that I know the backup has worked properly, because my lock screen works with the correct swipe pattern, and when the lock screen is on I can see my background behind it. But then I unlock in - and it's just a black screen with the notification bar.
What should I do now?
I used to use the "Advanced Launcher" and I may have inadvertantly replaced the original launcher. Is there any possibility that this could be because the new launcher has got corrupted or moved somehow?
This is so frustrating because I know I'm almost there! The backup works, except for this whole black screen thing.
Also, should I try restoring the nandroid backup again of (4.0.4) and then running the fix permissions again from recovery console? Any chance that might sort it out?
UPDATE: I've discovered all of my problems seemed to be due to a FUBAR SD card. I wiped, went back to factory, did the stock-to-CM process all over again. Phone STILL either wouldn't boot or would boot but nothing would work with my 2GB card in it. So I formatted a 1GB card I had laying around with 32MB swap, 200MB ext4, and about ~770MB fat32.
Phone now works better than it ever has on any firmware since the day I bought it! It's a lot faster than it's ever been, too. This also explains why I couldn't restore my Nandroid backups. Nandroid and Backup for Root both work great now (and are lifesavers!).
I no longer have any complaints about CM!
Original:
Thank you Mikey1022 for a nice warm threat of banning me for my first post ever. Really makes a newcomer feel welcome around here. My bad for thinking something to do with CyanogenMod and Nandroid was development-related.
Anyway, as was said in my thread that was locked:
The last few times I've updated to a new CM ROM, my phone boots to the android screen, goes black, stays there indefinitely. Have to pull battery.
OF COURSE I always do a Nandroid backup before flashing a new ROM. So I think "well, I'll just revert to my backup." Right?!? No. Whenever I try to restore a Nandroid backup, I get "Error performing restore! Try running nandroid-mobile.sh restore from shell". When I run said command in adb, it tells me:
Verifying backup images...
boot.img: OK
cache.img: FAILED
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: OK
md5sum: WARNING: 2 of 6 computed checksums did NOT match
Error: md5sum mismatch, aborting
How does my cache and data images "fail?"
So I end up wiping, then re-flashing the CM update, and all is well. Except I have a wiped phone, with none of my apps or settings. I know, I know, I should wipe anyway, right? Bull****. I spend a lot of time customizing my phone, getting it just the way I like. I have tons of apps installed, set up how I like. To wipe every two weeks when CM releases a new update is absurd. I don't have to wipe my computer every time Microsoft issues a security update.
So my two questions are: Many other people report flashing the new CM ROMS without having to wipe, so why doesn't it work for me?
And why can't I restore a friggin Nandroid backup? Really, what is the point of making a backup if there's no way to restore it?
Notes: I have a brown T-mo G1 unlocked on AT&T. I just did this whole process today going from CM 4.2.3.1 to CM 4.2.4. I have CM's Recovery 1.4 installed. I have a 2GB SD card formatted as ~1.4GB fat32, ~500MB ext4, 64MB linux-swap. And I have an anxiety problem. I'm eating Xanax like candy.
I am completely with you that it is inconvenient to wipe and flash and have to put all your settings back together. I've also been lurking for a little while and learned that most people are dickbags about posting in the right forum, rather than just helping someone out. Don't take it personally.
The best thing I have found to do is get Backup for Root. I'd recommend MyBackup Pro as well, to be safe. Backup with both before wiping and flashing a new rom, and usually Backup for Root will restore your desktop and settings. Reboot a couple times if things don't come back instantly.
If I were you, I would just take some time out, copy the files on the SD to a hard drive, reformat the card, wipe the device, and reload everything fresh. But that's just me. Good luck
You can flash the restore through fastboot....
take the data.img and
fastboot flash userdata data.img
though if the md5 is messed up...its probably not a good idea, though at the worst you can wipe
B-man007 said:
You can flash the restore through fastboot....
take the data.img and
fastboot flash userdata data.img
though if the md5 is messed up...its probably not a good idea, though at the worst you can wipe
Click to expand...
Click to collapse
What he said. Put all your .img files in the tools of the sdk. In order, the fastboot commands would be:
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Cache and misc don't really matter that much. This will manually restore your nandroid backup.
Thank you very much, FaJu. That is exactly what I needed to know. I will try that next time if I can't get Nandroid to restore.
I also started backing up with Backup for Root, as drspanklebum suggested, so hopefully one way or another I'll make damn sure I can restore my apps and settings if need be!
UPDATE: I've discovered all of my problems seemed to be due to a FUBAR SD card. I wiped, went back to factory, did the stock-to-CM process all over again. Phone STILL either wouldn't boot or would boot but nothing would work with my 2GB card in it. So I formatted a 1GB card I had laying around with 32MB swap, 200MB ext4, and about ~770MB fat32.
Phone now works better than it ever has on any firmware since the day I bought it! It's a lot faster than it's ever been, too. This also explains why I couldn't restore my Nandroid backups. Nandroid and Backup for Root both work great now (and are lifesavers!).
I no longer have any complaints about CM!
So I'm running Fresh 2.1 and tried to upgrade to 2.3.3 last night, but it was putting it into an endless reboot. I made sure I wiped the cache and data so the only thing I can think of that's causing the problem is that I'm using apps2sd and didn't wipe my ext3 partition. Reflashed back to my 2.1 backup and things are back to running fine now thankfully. It's brought a few questions up for me, though
Before I go the route of wiping my ext3 partition for apps2sd I want to make sure I can still recover back to the way things were before in case the upgrade to 2.3.3 doesn't work. I use Clockwork ROM Manager with Nandroid to do my backups but when watching the backup take place it looks like it tries to mount the ext3 partition to back it up but fails. Honestly not fully familiar with how apps2sd really works, so I don't know if that failure during the nandroid backup means my apps on the ext3 partition aren't getting backed up. Would that mean that if I wiped the ext3 partition and tried to recover my 2.1 ROM that my apps would not be there?
I thought maybe I could just undo the apps2sd setup, do a backup and then I'd be fine. But I'm having trouble finding clear, up to date instructions for how to undo apps2sd.
If anyone can clarify any of my issues or point me in the right direction, I'd appreciate it. Thanks!
Could someone at least point me to some updated instructions for undoing apps2sd on the Sprint Hero?
pdragon said:
Could someone at least point me to some updated instructions for undoing apps2sd on the Sprint Hero?
Click to expand...
Click to collapse
The instructions you are looking for are here
Normally (at least in the RA recovery) when you go to the backup menu for nandroid, you can choose if you wish to backup normally or with the ext partition included (much bigger file, takes longer). Regardless, if you wipe your ext partition, and you need to nandroid back, the backup will work fine, you will just need to reinstall your applications.
I save myself some time when I need to do this by using "Shootme" (free on the market) and take screen shots of my apps, then I can just refer back to the screenies to find everything I need. Alternatively, you could use the ADB "pull" command and take a copy of your apps directory onto your computer, then push them back if needs be.
Hope this helps!
Thanks for the reply, runngwlf. I guess either the version of Nandroid I have, ClockworkMod Recovery, or my phone doesn't support backing up with the ext. When I go into Nandroid, my only options are Backup, Restore & Advanced Restore. Choosing backup just goes straight into running the backup with no choices. During the backup it gives an error saying it couldn't mount the ext partition.
Thanks for confirming the backup will still work, just without my apps. Guess I'll give it a shot!
runngwlf said:
...
Normally (at least in the RA recovery) when you go to the backup menu for nandroid, you can choose if you wish to backup normally or with the ext partition included (much bigger file, takes longer)...
Click to expand...
Click to collapse
Hah! That little tidbit got me going in the right direction. Looking through the ClockworkMod i saw an option to install RA Recovery as an alternative boot recovery. Lo and behold, rebooting into RA Recovery gives me that ext backup option. Thanks again!
Hi everyone!
After a year or so of using cm7.2 on the i9000 i'm now facing a reproducible boot loop:
As it occured the first time, i made a nandroid backup via cwm, did a factory reset and reinstalled cm7, which resolved the bootloop. As i restored the data from the nandroid backup, the bootloop occured again and kept doing so when i tried the whole procedure again.
Is there any way to get the data (SMS/Contacts/Apps etc.) back without the bootloop?
Every suggestion is highly appreciated, thanks in advance!
According to Google, SMSs are stored in /data/data/com.android.providers.telephony/databases/mmssms.db, and contacts are stored in /data/data/com.android.providers.telephony/databases/contacts.db (but they should be synced to your online Google account). Apps are stored all over /data/data I think.
i have accessed the backup via yaffey and found it, thanks.
the following might be a stupid question, but: how can i insert the exported files into the fresh flashed cm7?
Titanium Backup only let me restore the system files, but nothing from data/data :/
You could try to overwrite it (after backing up the current files) but I don't really know. I suspect these are simple Sqlite databasefiles.
rooted, stock lollipop 5.0.2, problem started out of nowhere this afternoon...
camera won't let me take photos as it asks for an SD card. even after i insert an SD card, the error persists.
opening quickpic gives me the following errors...
Code:
not an error (code 0) could not open the database in read / write mode
Code:
unable to open database file (code 14)
can't delete ANY files manually in ES file explorer even with root explorer enabled.
booted into TWRP and cleared cache and dalvik to no avail.
seems like the phone can't read or write any data, except installing/uninstalling apps via google play still works. seems to be the same problem addressed in this thread http://forum.xda-developers.com/galaxy-s2/help/read-write-errors-advice-solved-t2323801 although i don't know how to identify the corrupt file(s) and delete them or fix permissions...
help!!
...bump?
basically wen that happens is because a file or folder is corrupted, it maybe in any place on your phone really difficult to find. That usually happens after you flash some (app, script), restore a TWRP backup, or a app that have root access doing the wrong thing.
i had this problem two times.
In the 1°, i fix by going in the TWRP, and erased my internal memory, after reboot all good.
this case was very simple i copy every file to pc, erase, after restore the one i need, and everything was fine...
In the 2°, i try that and was not successful, i need to re install the stock rom via fastboot from xml rom file to completed clean my OS.
In both cases, i was not able to make a Titaniumbackup, so i lost some data of a fill apps in the second (because i make a backup every week, if i didn't have it i probably lost everything).
If you don't use titanium, and don't wanna to loose things and app files etc, you can try copy everything on internal and external memory, by plugin on the device to a PC, after a TWRP backup of yours data, after wipe, dalvik cache, data, internal storage, cache, system, re flash the same rom you are now, and after test and see if you can write, restore the data backup.
But that data may corrupted your phone again, because the problem maybe in that.
So if after restore the data all goes bad, redo everything and do not restore data, you will lose app and data, but app can be reinstated.
:good:
baybutcher27 said:
basically wen that happens is because a file or folder is corrupted, it maybe in any place on your phone really difficult to find. That usually happens after you flash some (app, script), restore a TWRP backup, or a app that have root access doing the wrong thing.
Click to expand...
Click to collapse
thank you, i used this as an opportunity to wipe and flash cyanogen. so far so good (seems much smoother too).