yesterday i did a nandroid backup because i wanted to update my PRL (so i flashed to a sense rom and then did a nandroid restore - had no problems at all). today i was looking at my free space on the phone and it was in the 60's - i remember when i first installed this months ago i had about 260 MB, and i barely have any apps, so i thought i'd run firerat's again. i don't know what happened, but i can't boot the phone - sits at the HTC screen and then goes to recovery. i tried doing a nandroid restore about 5 times - from the phone's recovery, once in fastboot, and once in adb on the computer. it says it's successful, and the system, recovery, boot and data files are 64.4 MB, 5 MB, 2.5 MB, and 308 MB so I know the info is on there (plus it worked yesterday).
if i do a 'df -h' though, it shows /dev/block/mtdblock4 using 1.1 MB mounted on /cache and that's it (well, it shows tmpfs at 0 MB too, but those are the only 2 things that show). what's weird is, if i do a 'df -h' WHILE the nandroid is restoring, it shows 61.3 MB in /system and 120.9 MB in /data. but once it's successful, all that goes away.
so, what could be keeping the backup from sticking??? any ideas?
i hope this makes sense - i tried to give as much info as i could, but keep in mind i have no idea what most of this means. lol. thanks for any help you can provide.
Try doing a full wipe - system/cache/boot/dalvik before you nand restore.
i had this problem once before, but for me it was due to the nandroid backup running out of space during the backup. it looked good, but it wouldn't restore.
lol, what's weird is that i DID wipe like 5 times and had no luck. for some reason, u telling me to do it made it work! (no, i'm not being sarcastic!). this time i used Fresh Kitchen to wipe the catch tho...for some reason i guess it wasn't fully wiping in recovery.
THANKS!
As long as is worked... we are good!
Related
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!
Hey guys, I have a memory issue with my Nexus One when it comes to available storage space. The rom available memory seems to get lower and lower everytime I flash a rom than the previous time. When I load roms like CM6 or Kang-o-Rang or MicroMod Supercircle 2.7 or any others I have 4-16 MB available and nothing has installed yet. I usually use A2SD EXT3 for these but now its extremely difficult to do anything when booting with so little space to begin with. A week ago, on most roms I have well around 150 MB free before installing anything. What may have caused this issue? I even tried booting CM6 with a different SD card not partitioned for A2SD and wiping everything and same result and now I really can't install anything. So is my phone faulty or is there something I can do? I am currently running recovery Amon RA 1.7.0.1 and issues seemed to have come up since using this recovery. I was using Clockwork Mod latest one before this a few days ago.
Any ideas?
Have you been wiping data + cache each time you flash?
Make sure you're calculating data space and not system space (which can be as low as it gets to be, it doesn't matter).
codesplice said:
Have you been wiping data + cache each time you flash?
Click to expand...
Click to collapse
I have wiped, cleared cache, delvik many many times. I suspect that the wipe is not working properly. I have tried two different recoveries and nothing works. My available space now running on Nexus FRF91 stock with root only I have 53.64 MB free. I have installed no third party apps yet whatsoever. I have not even logged in to google yet because it will download all my apps again. I have rebooted as well. I think theres an issue with my device and memory. Should I call HTC or my warranty is void?
Sounds like a weird problem, I would've tried to wipe a time or two more. I just wiped my device after flashing nightlies for the last two months without wiping and I noticed I had 170MB free when I booted up with a few apps installed.
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Jack_R1 said:
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Click to expand...
Click to collapse
I've tried everything except ADB command line. I will have to read into doing that as I am unsure what to do. I have wiped from recovery and through the rom at least 15 times each! lol
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Jack_R1 said:
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Click to expand...
Click to collapse
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
timahawk said:
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
Click to expand...
Click to collapse
I have this exact issue. I know how to wipe. I have gone as far as reloading HBoot and placing the stock EPF30 image. I have gone thru using clockwork and Amon. I know how to do factory resets. I know how to go to storage options with clockwork and format all partition options. I have spent months on this. Below is a readout, after blowing away everything.
~ # du -hc /data
du -hc /data
2.0K /data/lost+found
4.0K /data
4.0K total
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 192.9M 0 192.9M 0% /dev
/dev/block/mtdblock5 196.3M 109.5M 86.8M 56% /data
~ #
Another user that I have been working with has the exact issues as the user here and me. He contacted HTC. They are replacing his N1. There is something weird going on with some of these units. Just like a few months back, no one knew anything about the bad boot blocks issue causing many developers to change their ROM installs to accommodate those users with this issue. This low space on /data issue is another one that sooner or later will start to show up more and more, IMHO. For instance, at best using either Evils Sense Roms or MicroMods Hybrid sense Roms, I have 23MB free on initial install. This is after basically wiping formatting, resettings factory Data etc etc. At best, lets say using Enoms latest AOSP, I have maybe 75Mb free Internal memory, after initial install and NO applications downloaded installed on my part.
I really wish that folks here and on other threads would start to take this issue a little more seriously than basically saying a user isn't properly wiping his setup prior to an install. I have my beloved N1 since third week of January this year. Never had a problem with rooting, installing any of the original CM, or Paul M stuff from the early days here and on their Kitchen setups. Something has basically changed to cause these issues on a number of Nexus one setups. I have root explorer too and no manner of deleteing, via changing partition permissions from RO to RW makes any difference after wiping, formatting whatever prior to a fresh clean install of any current ROM.
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Saphroxx said:
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Click to expand...
Click to collapse
How did you install the nightly. Even with my issues of 109Mb used up on data before I install anything, I have the latest nightly running along with latest Gapps and approx 50 of my own apps, with 79Mb free internal. I used clockwork recovery, then under storage options, you can run format options, on boot, system, data, cache, and SD-EXT and then under advanced, wipe dalvik-cache. I also added the data factory reset option also. I then clean installed the nightly. Then after an initial setup to just have it running, flashed the gapps. I did initially have approx 75Mb free Internal before the Gapps install. Then I went down to 53MB after gapps. I verified I had the correct settings in settings:Cyanogen Mod for the file system. I then flashed the latest Dark Tremor script, ran the commands for a2sd check, a2sd reinstall, a2sd zipalign and a2sd cachesd to move the dalvik-cache to sd. I have an EXT3 setup on my SD card. After moving Dalvik cache I jumped from 28Mb free to 79Mb free where it's pretty much staying now. Not as much as others that don't have the issues on /Data but at least useable.
I've flashed custom roms many times, but I have a couple questions regarding Texas ICS p10.
Currently running:
MeDroid 4.1.
BlackRose with System 220MB Cache 16MB Data 200MB
Amon’s RA recovery
Here's a checklist of what I should do:
Backup everything.
Update Blackrose to system 210 / cache 8 / userdata 218.
Wipe everything / factory reset 3 times
What do I need to do regarding formatting/partitioning the sdcard? ext4? setting dalvik cache to use sdext or data partition? In Amon's RA recovery, I have a "partition sdcard" option, with options to
- Partition SD
- Repair SD:ext
- SD:ext2 to ext3
- SD:ext3 to ext4
Do I need to do anything to get a2sd working other than rebooting a couple times?
Flash Texas' p10.
Flash google apps.
Restore.
Done.
Thanks in advance.
Sounds like you got it
if you are ext4 from medroid, you should be fine--not sure, but ext3 may work too
your current partition sizes are ok
see this on a2sd
http://forum.xda-developers.com/showpost.php?p=21222591&postcount=1374
i think you only rin a2sd install one time
i went to p10 and tiamets kernel and had some issues, restored back to p9 and lost my app links--even a sdcard reformat didn't work with p9 so went back to a medroid nandroid
haven't had time figure it out
medroid 6.1 is pretty stable for me
Ken
How can I check if the sdcard is formatted as 4ext?
Isn't it dangerous having a cache partition of only 8 MB?
Sent from my Nexus One using Tapatalk
maybe gparted or a partition tool program
i am having sdcard issues atm so can't test--terminal em can check, forget command, but sometimes it wasn't accurate for me
i don't know that 8mb is dangerous--some larger apps may not work right--depends how rom handles them. cm7 handles them well--miui doesn't--or so folks say
Don't know about 8MB cache, but it's kinda vurnerable to have only 210MB system partition now. If you have any plan to switch to other ics rom, i.e. MeDroidMod, you'll only have a little size left, or even nothing left. I repartizied back to 220/16/200, which is acceptable for any rom.
Sent from my Nexus One
Ok, so I followed the checklist I listed above. p10 stalls at the blue X boot logo for 10 minutes now. Anyone know why it's doing this? I'm going to go do a full wipe/repartition/reinstall again. I left my hboot alone, as suggested twice.
Actually, I opened blackrose and it automatically installed the latest blackrose, which put my phone in recovery and apparently wiped the rom??? Anyway, now I couldn't change hboot partitions anyway, so I proceeded with the rest of the checklist...
Have a 220/16/200 partition?
Boot into recovery, if you have 4ext recovery, you can format everything except sdcard, then flash p10 & gapps.
Sent from my Nexus One
Yeah, I have that partition. I just wiped everything, repartitioned the sdcard and reflashed... currently 8 minutes in the boot animation...
Not sure what to do from here.
Installed latest medroid 1.3.2a and it just keeps booting back into recovery.... hrm.
Do I need to flash a boot img as described here?
http://forum.xda-developers.com/showthread.php?p=22731102#post22731102
Ok, it installed. Updating blackrose, which took out my ROM for some reason, reverted to the default hboot as far as I can tell. I put the 220 version back on wiped and reflashed and it booted just fine.
Ended up using Medroid 1.3.2a instead of TexasIce p10. Even though p10 has HWA, it has bugs (browser rendering on zoom takes 2 seconds, sometimes longer) and isn't as fast as Medroid in general.
just got 1.3.2a and is running great
samuaz is loading HWA version now, but may have same issues as T's
First boot on ICS may take a while ! Just chill out ^^
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!