yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] cdzo72:
Ok just flashed this new recovery and thanks to TheManii and all his efforts it went off without a hitch.

Now I'm posting so that others may get something out of my experience... since the new CWMs came out I have not been too happy because the backups take twice as long and take up twice as much space.

If you compare the two, my StreakMod backup is only 629 MB in size and takes about 6 or 7 minutes to take place.

The CWM backup is 1.12 GB in size and took almost twenty minutes on each of 3 backups I did. Now in theory this is not supposed to be the case, which is the entire reason for the new "blobs" folder which is supposed to keep files that haven't changed since the last backup and thus making the actual backup faster and smaller (but this doesn't include the blobs folder)

For those of you that may scratch your head, when the backup gets to "Freeing Space" and "Done freeing space" it may seem to be stuck, but after your first backup, this is the part of the process where CWM is comparing new data with the old in the Blobs folder and directing a reference in the backup of which files to look to in said folder (I think this is the way it is, correct me if I'm wrong).

In theory, old info is supposed to get deleted (I have 4 other devices using the new system and I have yet to see the backup get any smaller or get any quicker). The Blobs folder just got massive on my Galaxy S2 and Note, almost 6GB, so I deleted the old backups and the contents of the Blobs folder and just let it start from scratch and was back down to 1.2 GB.

Please don't erase or touch anything in the blobs folder after a backup if you expect to use it. You can erase it's contents like I do and THEN run nandroid, but not after.

Again, if I'm incorrect in any of this, please some one straighten me out because I'm still trying to grasp the changes, it seems to me the entire process has gone backwards in terms of space used and time consumed to run.
[Streak 5 Android Development] TheManii:
How nandroids work

CWM 6.0.1.2 makes it into a menu option instead of a hidden switch (but I cannot get 6.0.1.2 to compile)

To previous post:

I dont know why yours is taking so long: On my S5, it takes about the same amount of time as to generate *.img type nandroids. It shouldnt ever take longer then 10 minutes unless you're beyond the 2GB mark by having a ton of stuff moved to SD.

It will never be faster, merely the same speed at best. But it should be at best 20% slower and at worst it depends on how many files you have, but it will save a great deal more space over tar/imgs. (unless your nandroids have very little in common)

EVERYTHING is stored in blobs now, deleting it is the equvilent of deleting every nandroid you have: It doesnt merely store new/repeats. If you look at the actual nandroid, it's only ~200mb because system cant be deduped and for the boot.img+recovery.img. On my S7/S10 a nandroid is 35mb because all it's filesystems are ext (excluding the size of blob)

You cannot manually remove entries (reasonably), you must delete the nandroid you dont want and run a "free space" and it will remove unneeded files from blob.

There's no simple way to seperate nandroid sets to redistribute/whatever. You're better off using tars if you wish to redistribute or store away off of your sdcard.

You can also use tars and lose the benefits of *.dups, it is still officially supported in CWM. But for a while it was merely not used by default and required a hidden switch to use.

Tars are basically *.imgs but more suitable for ext partitions (in actual usage, they're not really anything alike format wise)
[Streak 5 Android Development] _2bad4u_:
I'm on miui 2.4.20 with a 4GB internal class 10 card (i removed the 2GB from dell), I have kernel test 4 from _n0p_, when i try to make backup it's getting stuck at dadadata, i waited 20 minutes and after 20 min it's showing me a black screen and i have to remove the battery. I tried the fix and i still get the same error. Don't know what to do more.
[Streak 5 Android Development] TheManii:
Did you flash the workaround?

Tell me what your /firstboot looks like
[Streak 5 Android Development] pjg_pigeon:
I believe i have the exact same issue when trying out paranoid. I have flashed the fixer. My firstboot contains

'lost+found' folder containing a single file 'obj' 2048 bytes without any permissions,,all info gained via es explorer.the file seems empty?

Hope this helps
[Streak 5 Android Development] TheManii:
If that is the case, then fastboot isnt being applied properly,

can you run it again and give me the contents of /cache/recovery?

I need to look at the logs. lost+found should be completely empty afterwards
[Streak 5 Android Development] pjg_pigeon:
Sorry should i Re-run fixer or nandroid?
[Streak 5 Android Development] TheManii:
Yes, run the workaround: i need the logs from it
[Streak 5 Android Development] TheManii:
Hmm, i dont see anything wrong with the log or the way you flashed it.

Is the file still there even after doing it again? Are you able to manually delete it?
[Streak 5 Android Development] _2bad4u_:
Please tell me how to save the log when the phone after 20 min shows a black screen and i have to remove the battery because is not responding, is the log available if i remove the battery.
[Streak 5 Android Development] pjg_pigeon:
Yes, i am able to remove file then retried a backup, But something new happened. I left the room while nandroid was stuck on 'datadata' when i returned the recovery screen just had the cwm logo in the middle of screen with the version no. on the very bottom of the screen?

[7:55 update] the obj has returned but this time as an empty folder again with no permissions set? Wierdly if i view permissions on its parent then es explorer gets stuck in loop and reports that it contains 4000 files and still counting
[Streak 5 Android Development] _2bad4u_:
What rom do you have pig_pigeon and kernel?
[Streak 5 Android Development] pjg_pigeon:
Please see the attached screenshot,
[Streak 5 Android Development] TheManii:
At this point it sounds like there's an issue with your device itself and the folder being full is just one symptom?

From your log it seems like that it's clearing it properly, so either it's not actually sticking or all those files are being remade rather quickly
[Streak 5 Android Development] pjg_pigeon:
Just letting you have some more info.

I have had a bit of free time on my hands today. After all my failures this morning with nandroiding paranoid and the rom being so laggy. I restored my dsc 1.4 via nandroid without any problem. I then nandroided a new dsc backup without any problems. I then flashed lxdroid to test that rom. But again I am unable to create a nandroid backup for lxdroid either.

I also tried renaming clockworkmod folder and re-creating a new empty version but the same issue with datadata still occurs.
[Streak 5 Android Development] TheManii:
when you flashed the fix did you immediately nandroid or did you let it boot first?

the root issue is that all these files in lost+found are being generated tha shouldnt be
[Streak 5 Android Development] pjg_pigeon:
I am fairly sure I immediately nandroided without rebooting. What's the correct method?
[Streak 5 Android Development] TheManii:
That's the correct method, I'm rather stumped why the files arnt getting cleared then.

The log shows that it seems to have succeeded and you're doing it immediately so it shouldnt have the chance to recreate them.

Depending on the rom: you could just try reformatting /datadata (ie /firstboot) and continuing from there. Non-stock based roms this is safe, stock based roms will force a fac reset unfortunately.
[Streak 5 Android Development] pjg_pigeon:
I am not sure i would even know where to start on doing that. Is their a guide?

Reading through this thread it seems I am not alone on this poblem, I am more than willing to try anything to help me or others.
[Streak 5 Android Development] TheManii:
To reformat only the /datadata partition, go to format -> /datadata in CWM.

Depending on your rom though this could force a full fac reset, so be aware.

I've tested the workaround and it seems to clear lost+found for my system, but I cant ever actually reproduce the part where it completely fills up.
[Streak 5 Android Development] pjg_pigeon:
That's fixed it I think.

Formatted datadata successfully.

Completed a backup successfully.

Rebooted successfully.

What's stored in datadata.I presume my backup although completed will have an empty datadata? Can I restore from this?

By the way thanks for all your efforts and help.
[Streak 5 Android Development] TheManii:
Depends on the rom, if you're using CM/AOSP/Paranoidandroid/MIUI /datadata simply isnt used at all period, so it wouldnt matter.

On a stock-based rom like DSC it would fac reset so this wouldnt help as you'd lose your data.

Dont know why the fixer isnt working for you though, a fac reset will definitely fix it 100% of the time, unless it errors out of course.
[Streak 5 Android Development] cdzo72:
Ok here's a different case for y'all to help me figure out...

I tried to flash the AOKP ROM and all I got was a bootloop so decided to go back to my nandroid of the Cyanogen7.2 ROM I was using...

Ok, now once I booted I'm getting a message that "Phone storage space is getting low" and the vast majority of my user apps are not even installed anymore

Any ideas?
[Streak 5 Android Development] Strephon Alkhalikoi:
What is the size of the system and data partitions on the ROM? On stock ICS, according to Google the system partition must be at least 250MB. I don't recall the size of the data partition but the numbers aren't really relevant here. What is relevant is that more than likely in order for these ROMs to work the internal partitions must be formatted to be larger sizes. This cuts into the amount of storage space available on the internal MicroSD. If you have a lot of apps installed on the internal MicroSD, the amount of space lost to the expansion of the other two partitions could be sufficient to drop the amount of remaining space past a given threshold. The end result: an error message pops up.
[Streak 5 Android Development] TheManii:
Reformat and show me the log, I'm 100% sure I got the size of the partitions correct.

You can of course try redoing in streakmod to determine if it's CWM or your device.

Do you know which partition it's complaining about? It could be due to any of system/cache/firstboot/data.

Afaik only the newest updater-binaries can even change the size of the partition, and it's only downwards (ie smaller then max).

The AOKP update.zip is using one new enough to resize the partitions, but it's not actually doing so, it's using the full size.

They cant resize larger though, the bootloader isnt designed for that fact (though this isnt really relevent to us, and it only applies for the NAND/MTD partitions, not the innerSD ones)
[Streak 5 Android Development] cdzo72:
I switched back to Streakmod and restored the nandroid I created before flashing CWM.

I can't specifically remember which it said but seeing as there were more than half of my user apps not installed when it booted I would have to guess it was the data partition...

So what I can do is make a nandroid in Streakmod to fall back on... flash CWM and let it boot... create a nandroid from CWM, reboot and then go into recovery and have it restore the CWM nandroid... and get you the logs of that nandroid process correct?

I've never run logcat during nandroid so not sure how to go about it but I'll research it... or do want logcat of what's going on during boot?

PS.... thanks for your help... I'm more than willing to be guinea pig since the Streak is no longer main device but I can't bring myself to get rid of it either:p
[Streak 5 Android Development] TheManii:
As far as the logs are concerned: reproduce what you did to make this happen.

Assuming /cache works: the log is in /cache/recovery.
[Streak 5 Android Development] TheManii:
If anyone can tell me why these errors occur and how to fix it:

prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function check_exist_file:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:158: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function isLargeFile:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:228: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function isLargeFile:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:232: error: undefined reference to 'fseeko64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function isLargeFile:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:233: error: undefined reference to 'ftello64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function getFileCrc:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:189: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function minizip_main:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:463: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libbusybox_intermediates/libbusybox.a(mktemp.o): in function mktemp_main:external/busybox/debianutils/mktemp.c:94: warning: warning: tempnam() possibly used unsafely; consider using mkstemp()
collect2: ld returned 1 exit status
make: *** [out/target/product/streak7/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1

This issue was introduced in

Add minizip tool. · 4e734a3 · CyanogenMod/android_bootable_recovery · GitHub:

It's some sort of issue in zlib, and until someone can tell me how to fix/workaround it, I cant build newer versions of CWM for any device.
[Streak 5 Android Development] TheManii:
Issue fixed, updated to 6.0.1.2
[Streak 5 Android Development] djmax81:
Clockwork Mod 6.0.1.2>>>> Is this beta too or its stable :) .?
[Streak 5 Android Development] cdzo72:
@TheManii... just as a quick question I was wondering if these new CWM recoveries would be able to create nandroids after using the ext4 data partition formatter from the following thread? I read this entire thread and I saw some mention of formatting the entire innerSD but was still unclear.

ext4 /data partition formatter by Kolteabhiman

I do remember flashing the script and noticing some considerable improvement (I'd like to think I noticed it, it's been awhile) and the only reason I undid it so to speak was because StreakMod was unable to create nandroids after the ext4 formatting...

Also trying the new CWM 6.0.1.2 this morning again. I had gone back to StreakMod after not being able to restore correctly from a nandroid if you may remember.... so what I plan on doing is the following...

Note: I'm currently using the CM7.2 ROM and _n0p_'s latest kernel DSC_Phoenix_CM-rel

1) creating a nandroid in StreakMod as an ultimate backup

2) flashing CWM 6.0.1.2

3) creating nandroid with your CWM 6.0.1.2 (had to jump hoops for nandroid to complete)

a) kept getting stuck at backing up datadata:mad:

b) tried 3 times to just flash CWM fixer and didn't work, still hung:mad:

c) so on 5th attempt I wiped cache, wiped dalvik, formatted datadata and then flashed CWM fixer:fingers-crossed:

d) after steps in c) I was finally successful in creating the nandroid :victory:

4) booting up a couple of times

5) factory resetting and booting a couple of times

6) restore from the nandroid created with CWM 6.0.1.2

Now, if you would like me to modify this process in any way to help you troubleshoot a problem I'm more than willing. I remember you mentioning that the recovery log was in the cache folder so here are two logs in a zip file, the names are self explanatory... one for the nandroid creation process and the second from the nandroid restoration process. I'm happy to say that the restoration did not give me the same issues as before where some apps were not restored after the nandroid...

Since then I have tried to create the nandroid again without all the steps 3a, b and c but no success... I have to do all that if I want the nandroid to be successful:(
[Streak 5 Android Development] TheManii:
Everything works except nandroid for a few users.

----------------------------------------------------------------------------------------

Well you were able to back up after reformatting /firstboot, so it only reconfirms that it's the issue.

I specifically need the log from it halting on it though.

All that's left is

Backing up datadata...
Fixing execute permissions for /datadata
lost+found

which basically means that it backed up an empty partition.

Restore back to the nandroid from step A,

show me the contents of EVERYTHING in firstboot and make a backup again.

Pull the batt after you felt like it took long enough, then show me the logs again.

Looking at the source of streakmod, I'm not even sure it does anything with regards to filesystem health. It doesnt have e2fsck, mke2fs, tune2fs in it even (unless I'm mistaken). You cant fail something if you simply skip half the steps.

Though it shouldnt affect it at all (as /firstboot is always yaffs2), you shouldnt submit bugs if you're using ext4, as I'm not ready to support it yet.

-----------------------------------------------------------------------------------------

I dont know what kernals offhand mount /data and /cache as ext4, I think DSC does.

But if you format to ext4 and try to mount as ext3: you cant. It will simply error out and you'll boot loop as you cant mount the partition in question.

Assuming that tool reformats properly to ext4.

streakmod definitely doesnt (properly) support ext4 obviously, as it was released before ext4 was even used in any rom (officially).

That aside, I am interested in making a varient of CWM/S5 to support ext4 partitions.

The main issue is that while you can mount a ext3 partition as ext4, you cant mount a ext4 partition as ext3 for the reasons above.

The right way to do it is to make seperate builds of <whatever rom> (or at least seperate kernals, as that's where the script is to mount the partitions on boot), so you dont end up with users trying to use the mod and end up boot looping.

Regardless I'm going to wait until I'm able to install a larger innerSD before investigating this further.
[Streak 5 Android Development] elsaghir:
Thanks

Thanks, I updated my DS to 6.0.1.2 and it works great so far.
[Streak 5 Android Development] jamo59:
jamo59

Hello there!

DSC 1.5 ROM now I have above. Unfortunately, the backup failed

Clockwork Mod 6.0.1.2 with!

Unfortunately, I had to put back at 3.2.8.

the backup process has completed! Go to start then freezes for a while.

The strip only to the rescue....
[Streak 5 Android Development] TheManii:
I'm going to need more info,

repeat the process and send me /cache/recovery/last_log
[Streak 5 Android Development] cdzo72:
The recovery does do everything its supposed to do... but when you first begin to use it there may be a few glitches you need to iron out...

Now I generally say to someone to read a thread but for this CWM project you REALLY REALLY do need to read the entire thread so you can see what we users have experienced and how to deal with issues to get the benefits of TheManii's hard, selfless work that he donates to us...

You will read about a few things to clean up and something to flash and where to find the logs that will TELL you what went wrong when something failed...

Once you get it all figured out then it should be smooth sailing from there...

I have a post from about 2 weeks ago detailing how I got my first successful nandroid backup and then restored. Once the first was done I haven't had any issues since.

_2bad4u_ also had some trouble and also provided some good insight in to how he got it working

Yeah it may have been easier to just give you links but then you wouldn't be motivated to remember the steps you took

Good luck
[Streak 5 Android Development] jamo59:
the backup process has NOT completed! Go to start then freezes for a while.

The only relief is ticklish. Several times I tried!

It is important to save, because each type of ROM, made ​​a nandroid backup, and if you think back a few minutes I will be healthy enough to ROM!

The forums can be found all the ROM's nandroid backup!
[Streak 5 Android Development] Adi Shakthi:
@all›>>>>>>>>>>

Plz provide an flasheble zip so that we can flash the latest rocovery (6.0.1.2) without using an pc .........

Adi.
[Streak 5 Android Development] djmax81:
To Manii :)

Hi.! Manii can send me link attach streak5sd8 Please :) ...urgent :good:
[Streak 5 Android Development] TheManii:
[Guide][Beta][Prelim]How to switch innerSD layouts
[Streak 5 Android Development] djmax81:
non of links working .!!! sorry

dude not single link working think server down .. can please upload the file
[Streak 5 Android Development] deysmacro:
yup .. confirm at time of posting this...
[Streak 5 Android Development] djmax81:
Its .! Not :banghead: sir
[Streak 5 Android Development] deysmacro:
well.. here is the download link.. dont sulk :D

streak:

http://www.mediafire.com/?a44fd15bfndg640

streak5ex:

http://www.mediafire.com/?jicyc4baaz6phij

streak5sd8:

http://www.mediafire.com/?aw4y4fnf810159r
[Streak 5 Android Development] citric_acid:
is cwm rom manager working with this recovery ?

https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en
[Streak 5 Android Development] deysmacro:
nope... our streak rom is not meant to be there.. unless TheManii have done something for the cwm here..
[Streak 5 Android Development] Adi Shakthi:
IS This CWM RECOVERY ......?...

Going to flash now ......

Thanx yar.....

Adi…
[Streak 5 Android Development] rsfinsrq:
Yes, 6.0.1.2
[Streak 5 Android Development] citric_acid:
what?? :silly: a flashable recovery lolx
[Streak 5 Android Development] rsfinsrq:
Yes, to update from previous CWM versions.
[Streak 5 Android Development] citric_acid:
oic so it works only if you have CWM recovery installed what about streakmod recovery, will it work ?
[Streak 5 Android Development] rsfinsrq:
Yes, StreakMod is CWM based.
[Streak 5 Android Development] djmax81:
Hi.!!!! manii ,there is issue after i tried all ..patch n fixes...still get stuck on backingup data.data on cw sd8 recovery.so can i just use cw ex inted ? No right.? :screwy:
[Streak 5 Android Development] rmriggin:
same for me stuck at datadata with softkeys flickering occasionally. Been letting it sit for the past 15 minutes but doesn't appear to be changing.
[Streak 5 Android Development] deysmacro:
you guys should use streak5 download link .. streak5ex and streak5sd8 is pretty much more advanced (i think) ...