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!
Related
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!
So I had my phone working and decided to try a kernel found here.
I went on, flashed the kernel through cwm, and nothing worked (stuck at loading screen with continous reboots).
So I flashed my recovery image, rebooting stopped by stuck it was at the loading screen anyhow.
So, since I could not come out of it, I downloaded a stock rom (I was running stock by the way), flashed it (with smartflash), rooted it (superoneclick), installed cwm (now v5) and I'm back on.
So I flashed the recovery, and most of the data is back but I lost all the apps on the SD card.
The SD card is the same from which I flashed the recovery image through CWM, and all my music is still there.
So might it be possible that the apps are still there too?
What can I do?
Why all the SD apps disappeared?
Edit: ok maybe we're talking about internal SD card... may it be the CWM v5 doing recovery from a v4 zip?
had this problem very, very, often...
nobody really could help me, but i know, its because of problems with the android_secure folder.
so i´m not an expert and i really don´t know what s the reason, but i tried some things and sometimes it helped...
it can appear if something goes wrong when you install an app or move an app from phone to sdcard, or when you want to restore them with titanium or cwm.
the possibiltythat it happens increases when you do both at the same time or, move many apps at the same time p.e. with gemini or install many apps at the same time (p.e. with panda pc suite).
or if something goes wrong with a market update.
mostly, it starts that you can´t install apps anymore. after reboot all apps on sd are away.
with luck you can repair it and get the apps back.
-delete the market cache.
-delete file smdl2tmp1.asec in android_secure folder on sd card or in mnt/... secure.. damn forgot the path of the second folder where this file can be. gotta google for it.
-or create a new android_secure-folder. unmount sdcard. rename android_secure folder to something different, so that there´s no more an android_secure folder. put sdcard back in the phone, reboot the phone. there will be a new empty android_secure folder. shut phone down, put sdcard into pc again, copy all files from renamed folder to the new android_sd folder, put card back into the phone, restart it and wait. with luck, your apps are back again.
don´t now, maybe it helps when you delete dalvik cache and cache before restart. sometimes it worked, sometimes not.
in your case, your apps are away after restore and not because of install/move2sd issues... so in this case its important to completely delete android_secure folder before restore. make a fullwipe. and after fullwipe i would restart phone once, so that a new clean android_secure folder could be created. hope something helps.
edit:
i did a little trick, that my external sd is mounted as sdcard in my phone. so normally the internal sd card is the "sdcard" in the phone. so, cos you can´t put your internal sd into the pc, you gotta mount it with usb connection.
Thanks but I'm afraid in this case the content really got deleted after I reflashed the rom...
IS there a way to really save everything via cwm?
Or should I use another software?
Also if flashing baseband: what will get deleted?
Flashing baseband will wipe /data
Rusty! said:
Flashing baseband will wipe /data
Click to expand...
Click to collapse
And how does /data relate to my problem?
Is /data backed up by cwm or not?
What is not backupped by cwm and how to backup it?
Rusty! said:
Flashing baseband will wipe /data
Click to expand...
Click to collapse
but you can restore it with nandroid, right? it's going to be just as before?
punyategar said:
but you can restore it with nandroid, right? it's going to be just as before?
Click to expand...
Click to collapse
If you mean baseband then the answer is no. It restores your ROM and all the apps including their data.
punyategar said:
but you can restore it with nandroid, right? it's going to be just as before?
Click to expand...
Click to collapse
Assuming you remembered to back it up yeah.
My radio flash procedure is:
NANDroid backup
Smartflash radio
NANDroid restore
Push new RIL
Use phone
Rusty! said:
Flashing baseband will wipe /data
Click to expand...
Click to collapse
I don't think so.
Kdz tool and official updater didn't wipe data. (Aren't you ?)
They did change only baseband and systems.
But you have to nandroid backup to avoid bricked.
You may not think so, but it does.
kitty's_daddy said:
I don't think so.
Kdz tool and official updater didn't wipe data. (Aren't you ?)
They did change only baseband and systems.
But you have to nandroid backup to avoid bricked.
Click to expand...
Click to collapse
Definitely wipe /data
Both Rusty! And myself always test new basebands and it definitely wipe /data.
Edit: sorry I'm referring to smartflash.
temasek said:
Definitely wipe /data
Both Rusty! And myself always test new basebands and it definitely wipe /data.
Click to expand...
Click to collapse
I think you would be correct.
It's only my opinion.
i use kdz tool, no user data will lost, only system(happened on me 2 times). don't use smartflash it will wipe all data
kitty's_daddy said:
I don't think so.
Kdz tool and official updater didn't wipe data. (Aren't you ?)
They did change only baseband and systems.
But you have to nandroid backup to avoid bricked.
Click to expand...
Click to collapse
dont know about kdz, official updater didn't touch my /data at all. i mean, my apps were just as before, the settings...
just use titanium backup and make sure the save location is in the sd card
For certain apps that have their own way of saving data, it might not always work.
I just can't find the correct answer in the posts I've read so far.
If I flash a kernel that doesn't work, and then I restore a CWM backup, why it wouldn't boot again?
If I reflash the stock rom and then restore a previous CWM backup, why something won't be there?
What exactly should I do in CMW to obatin a complete backup?
Or should I use something else?
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.
Hello
I'm pretty sure that my /data partition was corrupted. Not sure how, maybe using a custom recovery with the ICS kernel, maybe some other way, but it can't be formatted, copied to etc.
I've been reading on some other devices about editing the .pit file after finding out where the corruption is. I'm having trouble using LInux tools since using adb, I don't get the root command prompt, just a $.
Anyone have experience on a P7300 about how to work around the corruption, identify, perhaps run a fsck on the partition?
I'd also be willing to pay a $50 reward for anyone who can get it running again, even with a reduced size data partition, but ideally I'd like to try repairing the damaged partition first.
Thanks
Harry
check "Guide & ToolKit" thread
http://forum.xda-developers.com/showthread.php?t=1406137
SOLVED
Discovered after reading the Toolkit and guide that it wasn't an EMMC bug hard brick, thank goodness. I was directed in post #250 to one specific stock ROM to install with ODIN, that supposedly, was the only stock ROM that when you did a wipe data/factory reset, actually recreated the partitions and reformatted them. It is P7310XARLA3_P7310UELA3_HOME.tar.md5
But I had nothing to lose, so I installed the stock ROM with ODIN, booted the stock recovery, did the wipe, and for the first time in about 10 hours of trying this, it was able to format the /data partition, and installed the bootable ROM. After that, I installed a CWM recover in the tar format, and now about to put my old ICS ROM back on, the one in the development section that came from an OTA leak.
Thanks, I hope this helps someone who has problems accessing their /data or /sdcard directories..
So I've searched quite a bit on this one and can't really seem to figure out what is going on.
I started on TWRP 2.7.1.0 and when backing up with adequate storage space I kept getting "backup failed". I tried 2.8.0.0, same thing, and finally 2.8.4.0 failed as well. I cleared a bunch of stuff off of it and was able to backup once. Two days later when I was going to try out a new rom, I decided to make a new backup and right back to where I am now - fails every time. I have 10gb free and the backup is less than 5gb. I was getting impatient wanting to update my rom, and figured since I already had one backup I may as well try to install a new rom - I tried to wipe data/cache/dalvik, and even that failed.
I attached two logs I saved from different backups. I've tried fix_permissions and nothing. I'm assuming this may be a error with the internal storage, perhaps my next step would be to format that partition (Is this just "format data" in TWRP wipe section?)
Thanks for the help!