Develop Bugs

Nandroid issues Please help

Hey guys. I have done numerous nandroid backups in the past with problem but now I seem to be having issues doing backups.
Im running clockwork 2.5.0.1. I got to a backup and it sits there for a time and then spits out:
"No /sdcard/.android_secure found. Skipping backup of applications on external storage.
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backup Complete!"
Any ideas wtf is going on?

I think it all refers to Apps on your SD card. If you don't have any installed there, there obviously won't be anything to backup, & i believe the sd card has to have an ext partition, so as long as you don't have apps on your card, looks normal to me.
If i'm wrong, someone feel free to correct me.

I concur. If you don't have apps2sd going you won't have any ext partition on your SD card to worry about.

[Q] Q(s) does cwm 3.0.0.5 restore/backup sd-ext

Hi,
I searched various forums but cant find an answer to this.
Does cwm 3.0.0.5 backup and produce an sd-ext.img?
I recently got a replacement sd card, so I did a nandroid backup after I flashed cwm 3.0.0.5.
I copied this to my laptop, and g parted my new sd to have 2 partitions fat 32 first and the last 2 gb as ext3, as per the requirement for modaco no sense kitchen rom (a2sd+ version).
New sd in desire, I copied the whole clockworkmod folder onto the new fat32 partition.
Wiped everything I could using recovery (clockworkmod folder still remains present).
Tried to restore but got a message at the end that "sd-ext.img not found. Skipping restore of /sd-ext. Restore complete."
When I boot the desire gets past initial alpharev s-off replacement image I have (I have s-off), then presents a blank screen. This does eventually boot. However all apps are not installed. I assume that the original dalvik cache was not transferred and was reconstructed by the restore with what it had.
Is this a known problem with 3.0.0.5?
Is there another version I can flash which doesnt have this problem?
Just to provide all possible info require (I think). My desire is PVT4.
Thanks in advance.

I used CWM 2.5.0.7 from the alpharev release.
In my backup folder, I have sd-ext.img present.
I created this sd-ext with CWM itself. (I did a backup of the sd and formatted it)
So no doubt that CWM 3.0.0.5 did the same.
First, check if you actually have the sd-ext.img file.
Second, you might want to try to update to CWM 3, since the alpharev release is 2.5.1.8.

Well CWM will create the sd-ext.img backup if it detects that the partition is there. If out doesn't detect it then it will skip it like it did. There is nothing wrong with cwm at all and out works. You could upgrade your recovery to 3.2.0.1 but it won't make a difference really. Only way around it is to use titanium backup as it will restore straight to sd-ext
Swyped...

Meaple said:
Well CWM will create the sd-ext.img backup if it detects that the partition is there. If out doesn't detect it then it will skip it like it did. There is nothing wrong with cwm at all and out works. You could upgrade your recovery to 3.2.0.1 but it won't make a difference really. Only way around it is to use titanium backup as it will restore straight to sd-ext
Swyped...
Click to expand...
Click to collapse
Hi,
I used gparted to firstly create a fat 32 partition then secondly a ext3 partition (for apps) on a new sd card. I cant see a sd-ext.img file in the nandroid backup file produced by cwm 3.0.0.5 so I assume that it cannot detect the ext3 partition.
Do you have any idea as to why this is? Can I have done anything to help cwm "see" the partition.
I'll update to 3.2.0.1 to try if the same problem occurs in that release.
I take your point that I could use titanium backup to achieve the same. I dont really want to do this as as I find it a pain to re-install the large number of apps I like to carry about on my desire. The problem is that I know what runs well on a ext-3 partition and what only runs on int or system space. I only allow apps into system or int if I really them to be there so this means thatyou have to manually install each one of them to the relevant space. Also I use ext3 for dalvik cache (seems to improve performance).
I cant see a reason why 3.0.0.5 didnt see the ext3 partition and ideally I would like a nandroid recovery solution that could auto detect all partitions if present (as I guess many others would).
I'll update this thread when I have run through the update to 3.2.0.1 and done some more testing.

I think CWM doesn't backup ext-partition if there's no data

try the old CWM.. the one comes while you root with unrevoked3 .. coz I have old CWM and it does backup sd-ext.

[Q] Restoring nandroid backup on new sd-ext partition

hi, first, i searched but didn't find something that fits this question, so...
what happens if i restore a nandoid backup from a rom with ap2sd+ with a 512 mb sd-ext partition on a new sd card with an sd-ext partition with 2 gb?
Also the old sd-ext partition was etx3 and the new is ext4 formatet, will there be problems or does anyone did this kind of restore?
Or is it worthless and i should flash the whole rom again?
Thanks

Far as i can tdll you shouldnt have problems, all its doing is writing data..

it should work fine
there shouldnt be a problem as long as the rom supports ext4
i suggest backup your current rom
try restoring old rom
if it works - congrats
if not - flash new rom
it'll only take 10 mins of your time
and you get to learn something new

Hell yeah! I restored my nandoid backup of LeeDroid 2.5 Final A2SD+ and all worked fine, no problems, no need to flash again.
Greetings Spazzt

Not able to restore my nandroids properly anymore

So here's my problem guys (bear with me here ! , it takes a lil explanation ) :
i've had my arc for almost a year now, i'm using link2sd with a 2nd partition on my sdcard for linking my apps to help free up some internal memory , i also use CWM "back and restore" frequently and this is how i do it :
as a full nandroid backup would take nearly 1Gb of storage , i instead backup only the system and data files(less than 400Mb), manually calculate the md5sum for it, and then resore it when i need , and it has worked for me till recently , now when i restore the backup, i only get the system settings and the apps on my internal storage, no sdcard apps and no linked apps (previously it restored everything properly) , so my question is :
is it a Rom or kernel related issue ??. is there a way to fix it ?? or do i have to do a full backup from now on ??
btw i'm currently using JJ'Hybrid and arknight kernel 3.3 RC.
i know it's a long one guys , so thanx in advance .

You'll need to backup data from sd or sd-ext, which would need a full nandroid backup. I found the best compromise to save space is to backup, rename the backup to id it(eg aokp4),copy it to my pc, and only keep the newest one on my sd card.

sinkster said:
You'll need to backup data from sd or sd-ext, which would need a full nandroid backup. I found the best compromise to save space is to backup, rename the backup to id it(eg aokp4),copy it to my pc, and only keep the newest one on my sd card.
Click to expand...
Click to collapse
yeah i know, but that doesn't answer my question , why was it working before and now it's not , thanx anyway

[Q] CM 7.1.0 Complete System Lost

Hello everyone,
I had CM 7.1.0 on my Desire for a long time.
I used S2E to move my /app partition and another big partition (dont know name any more and cant look) to my sd-ext and it worked for a long time.
Yesterday my phone said space on the /data partition (150mb) is nearly full (warning on 15mb left) and I moved the partition to sd, too.
It said I should reboot and after the reboot my whole system was gone.
Now I have a stock CM 7.1. The home button didnt work either, I couldnt get back to home or display the task switcher, every other button still worked.
Strangely 4 apps from my previous system remained: Aldiko, Teamviewer, Tetris and little piano. Aldiko even has my whole Ebook Library from the previous system but settings and bookmarks were lost.
But I found out that my whole picture gallery is still there.
My contacts (not synced) were on the phone and now are they lost, too.
In the recovery I tried to mount all partitions, but after every reboot the sd-ext partition was still unmounted. I tried to fix permissions too. Didnt work either.
My English is not the best and I dont know if I made a mistake.
But I really need your help quickly to get back my old system.
Best Regards

If you have a nand backup just restore if from recovery.

If I had one I wouldnt ask this urgently ^^

if you want to keep all your apps and settings, this could be quite difficult.
try:
- reflashing the rom without wipe. i don't know if this will work to be honest, if your data partition has actually been moved and got corrupted, i don't know of a way to recover it.
- if possible install titanium backup, and if it can see your apps back them up, because it would be better to start all over from this point.
if neither of these methods work, then the 'easiest' way is to full wipe and start all over again (you will lose all apps + settings etc. your photos are still there because they're on the FAT32 partition of your sd card).
the problem you had is that you are still on stock hboot, so your small data partition fills up quickly. you shouldnt have to move it to sd, as it runs better/faster from internal nand memory. you had a large part of system partition unused, so so your overall objective should be to s-off and switch to cm7r2 hboot.
in summary from your position i would:
1. (make sure sd card is properly partitioned using gparted, 1-1.5GB maximum ext4 depending on number of apps you have)
2. s-off using revolutionary (think this is possible as your phone is still booting?)
3. change to cm7r2 hboot
4. boot into recovery, format all partitions except sd card (format system, data, sd-ext, cache, dalvik...everything so clean)
5. install rom
6. install S2E if this is your preferred method, just move apps to sd-ext.
7. restore apps if you managed to make a titanium backup
8. (if you start to run out of space again, then use S2E to move dalvik as well)
general guides for revolutionry, changing hboot etc here
in future:
- always backup your contacts to google
- i know it's easy to say this now...but have a nand backup before making big changes like this, and keep a few on your PC for safe keeping (they're stored in sdcard/clockworkmod/backup)

ghtwex moratus
A Big Thank You eddiehk6!
So you think it wasnt my fault, the partition got corrupted?
Strangely my phone space (150mb) on the stock CM 7.1.0 is full.
I would like to start from scratch and try your MildWild ROM the only thing I need very badly are my contacts.
Is there a way to extract them?
Btw I already have Revolutionary S-OFF
Best regards

Daniel2650 said:
A Big Thank You eddiehk6!
So you think it wasnt my fault, the partition got corrupted?
Strangely my phone space (150mb) on the stock CM 7.1.0 is full.
I would like to start from scratch and try your MildWild ROM the only thing I need very badly are my contacts.
Is there a way to extract them?
Btw I already have Revolutionary S-OFF
Best regards
Click to expand...
Click to collapse
don't know whose fault, but moving critical data partition sounds like a bad idea anyway...
your phone space can easily fill up because it's so small, 150MB can quickly be taken up by data/dalvik cache. stock hboot is also very wasteful, you probably wouldnt have fun into this problem if you were on cm7r2 hboot.
no idea how to extract contacts out a non-booting rom. if you have an old nandroid backup you could try restoring it to extract contacts from there, that's the only way i can think of. when you sync your contacts with google you'll discover how useful it is for situations like this...
at least you are already s-off so relatively easy from here.
not "my" rom lol, but i like it!
- change to cm7r2 hboot
- full wipe all partitions except sd
- install rom
- read OP for setting up app2sd by default (assuming you have correctly partitioned sd card with gparted or 4ext recovery)
regardless of what ROM you decide, use an app like 'diskusage' to check how all your partitions are being used, very useful for troubleshooting "low space" issues