yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] NYLimited:
I wonder what would account for such different results.. When you say your restore was unsuccessful do you mean it never finished restoration or did it finish but couldn't boot?

---

Definition of an update: take old bugs out, put new bugs in.
[HD2 Android NAND Development] clyder:
It couldnt't boot. I had to flash a kernel to boot. Then I realized that the boot.img file created on SD card was corrupted.

edit:

I did another test.

-Installed 5.5.04.

-did full backup

-wipe

-full restore / boot failed at start

-full restore from a backup made in 5.0.2.6 / boot failed again

-flashed back 5.0.2.6

-restored backup made in 5.5.0.4 / boot failed

-restored backup made in 5.2.0.6 / booted OK

So 5.5.0.4 definitely is not working for me.
[HD2 Android NAND Development] YZ:
Have I been on the PC for too long? I can't find the link to your dropbox in your sign :confused:

NVM, find it in your first post ;)
[HD2 Android NAND Development] Benik3:
I have problem with installing CWM via DAF (http://xdaforums.com/showthread.php?p=23143199#post23143199), so can I do it like this:

Repartition of MAGLDR to 150MB, catch 44MB.

Load CWM from SD card.

Instal CWM to NAND from zip

Also you wrote in OP, that is not recommended use flag filesize.

So delete the filesize in flash.cfg in recovery rrecov|ro|nospr filesize recovery-raw.img ?

(If I will get DAF to work...)

Thank you :)
[HD2 Android NAND Development] NYLimited:
OK, the (hopefully) last word on the 5.5.0.4 version for you. A little while ago I did a complete backup with 5.0.2.7 and 5.5.0.4. Nothing was different on the phone except the recovery partition - the phone was not even booted between the 2 backups.

Looking at the files created by the 2 processes they are identical except for one minor difference.

The boot.yaffs2.img files, for example, compare byte for byte and both contain the previously missing two files.

The only difference I found was the cache.yaffs2.img file (see below) which I cannot explain. I can send you the files if it'll help.

Here are the files created by the 5.5.0.4 as seen when copied to Windows:

03/01/2012 20:02 182,321,664 .android_secure.vfat.tar
03/01/2012 19:59 3,081,408 boot.yaffs2.img
03/01/2012 20:02 19,008 cache.yaffs2.img
03/01/2012 20:01 7,104,768 data.yaffs2.img
03/01/2012 20:11 359 nandroid.md5
03/01/2012 19:59 5,242,880 recovery.img
03/01/2012 20:09 804,931,584 sd-ext.ext4.tar
03/01/2012 20:01 139,191,360 system.yaffs2.img

And here are the 5.0.2.7 files:

03/01/2012 20:16 182,321,664 .android_secure.vfat.tar
03/01/2012 19:59 3,081,408 boot.yaffs2.img
03/01/2012 20:13 3,081,408 boot.yaffs2_.img
03/01/2012 20:16 95,040 cache.yaffs2.img
03/01/2012 20:15 7,104,768 data.yaffs2.img
03/01/2012 20:24 359 nandroid.md5
03/01/2012 20:13 5,242,880 recovery.img
03/01/2012 20:22 804,931,584 sd-ext.ext4.tar
03/01/2012 20:14 139,191,360 system.yaffs2.img

I guess that should pretty much put it to rest now. The only thing that'd make it better for me would be the old progress bar (a little larger for my old eyes). :)
[HD2 Android NAND Development] arif-ali:
A very detailed report. That is very useful.

Can you send over the cache files to me as a PM, and I will have a look
[HD2 Android NAND Development] NYLimited:
You have PM ...
[HD2 Android NAND Development] NYLimited:
v5.5.0.4 2012.03.04

Wow! A bunch of interesting things Not necessarily all problems but here goes:

Display of information is now shifted to bottom line of the screen, scrolling up from there.

Progress line (graph) is overwritten with text.

Display of files being backed up (or restored) is displayed at the top of the android's head.

Confirm install from zip dialog adds 10 NOs and one YES line (like old versions?)

The cache file is different yet again (see MD5 list below).Note that all backups were created without ever booting the phone between backups (except to load a different CWR)

The 5.0.2.7 version creates a file of 156,288 bytes

The 5.5.0.4 of 25FEB version creates a file of 88,704 bytes

The 5.5.0.4 04MAR version creates a file of 223,872 bytes

I didn't do any restores this time.

Here is the list of MD5s generated by each of the versions.

Backup made with 5.0.2.7:

21d2fd55af25831eef2f5033dc6c3fd5	boot.yaffs2.img
0636e981529b38b2cbcc123faf65d24f	cache.yaffs2.img
cab5079331862695b57646aba1eaa96f	data.yaffs2.img
63c20f98847a88a33f3bdcd45a3b7cbb	recovery.img
1a094858085d5582692fe6fab68ad704	sd-ext.ext4.tar
71da4edfd8d87c09eb5e80d493c2fae4	system.yaffs2.img
557ca86c927cc4a6c8081d5f3f05ad62	.android_secure.vfat.tar

Backup made with 5.5.0.4 2012.02.25:

21d2fd55af25831eef2f5033dc6c3fd5	boot.yaffs2.img
f60ecf1b7319c1dda579a20502930d56	cache.yaffs2.img
cab5079331862695b57646aba1eaa96f	data.yaffs2.img
abfd2d0374498800eb6c7b3538274e85	recovery.img
1a094858085d5582692fe6fab68ad704	sd-ext.ext4.tar
71da4edfd8d87c09eb5e80d493c2fae4	system.yaffs2.img
557ca86c927cc4a6c8081d5f3f05ad62	.android_secure.vfat.tar

Backup made with 5.5.0.4 2012.03.04:

21d2fd55af25831eef2f5033dc6c3fd5	boot.yaffs2.img
0dffd0268adcf040c16ef6f118ec05c0	cache.yaffs2.img
cab5079331862695b57646aba1eaa96f	data.yaffs2.img
abfd2d0374498800eb6c7b3538274e85	recovery.img
1a094858085d5582692fe6fab68ad704	sd-ext.ext4.tar
71da4edfd8d87c09eb5e80d493c2fae4	system.yaffs2.img
557ca86c927cc4a6c8081d5f3f05ad62	.android_secure.vfat.tar
[HD2 Android NAND Development] NYLimited:
v5.5.0.4 2012.03.11 - no visible change

Reviewing the 20120311 posting of 5.5.0.4 I cannot see a difference from a cosmetic or user's point of view. While there may well be changes within the code I cannot ascertain what those are.

Essentially, all the files created by v5.0.2.7 and v5.5.0.4 are byte for byte identical except the cache.yaffs2.img and the recovery files. The 5.0.2.7 version creates a file of 19,008 bytes and the 5.5.0.4 version creates one which is 92,928 bytes long. This difference has existed within these two versions from the start although I do not know what accounts for it.

My guess would be that the 5.5.0.4 version should restore OK since the important files are identical but I did not try this.

The MD5 for the files created by 5.0.2.7 is:

21d2fd55af25831eef2f5033dc6c3fd5 boot.yaffs2.img
ea1b9b7487013b63b4b97cd0ff479005 cache.yaffs2.img
77fc18af7681d4453b662f51896bed77 data.yaffs2.img
63c20f98847a88a33f3bdcd45a3b7cbb recovery.img
e343410ff979a4acf0cb5818edc0376f sd-ext.ext4.tar
a8bd5cb34fc6e8123836c73b7181bacd system.yaffs2.img
18d68a60f9cee54bad32cc6dda9afff4 .android_secure.vfat.tar

The MD5 created by the 5.5.0.4 version is:

21d2fd55af25831eef2f5033dc6c3fd5 boot.yaffs2.img
70822fbb6abd42f0058be8c1279c635b cache.yaffs2.img
77fc18af7681d4453b662f51896bed77 data.yaffs2.img
8b3272dfc8b2f3ec6b49b0ba62a6740a recovery.img
e343410ff979a4acf0cb5818edc0376f sd-ext.ext4.tar
a8bd5cb34fc6e8123836c73b7181bacd system.yaffs2.img
18d68a60f9cee54bad32cc6dda9afff4 .android_secure.vfat.tar

Note that the only differences are the cache and, of course, the recovery partition which is, in fact, different.

Since I don't know what the difference are or why I am again returning to the 5.0.2.7 working version.

Additionally, the display is still odd since the scrolling of the info starts at the very bottom of the screen, eventually overwriting the progress line indicator. The file names being backed up is still displayed at the top of the android's head. Seems a little out of whack to me. :confused:
[HD2 Android NAND Development] NYLimited:
I forgot to mention that this version still has the multiple line confirmation (1 yes and 10 or so no lines). Yuk. :-)

---

You can never learn anything by doing it right!
[HD2 Android NAND Development] MarkAtHome:
Try instead:

recovery rrecov|ro|nospr 5M recovery-raw.img

___________________

Sent from my HD2 ICS CM9 with XDA Premium
[HD2 Android NAND Development] NYLimited:
I always thought that a full backup created with this (v5.0.2.7) is like an image - so you can rebuild 100%.

After some experiments I decided to fully restore my device but found several little things missing after the restore.

As an example, I use a special app to sync contacts and calendar entries with Outlook which is my primary source (master) for these.

It creates a special contacts account which is not synced with Gmail.

All my apps (email, sms, dialer, etc.) see the contacts without a problem.

Yet, after the full restore there were neither contacts or calendar entries on the phone. I had to restore them from Outlook.

How can this be if this recovery does a full backup?

---

How come wrong numbers are never busy?
[HD2 Android NAND Development] MarkAtHome:
Where does the app store its data?

After restoring, did you remember to configure the app to look in the same dir?

Doing so might auto-magically restore the data after exiting and then relaunching. Can't hurt...

___________________

Sent from my HD2 ICS CM9 with XDA Premium
[HD2 Android NAND Development] NYLimited:
Not sure but I think in

/sd-ext/data/com.android.providers.contacts

Cannot specify folder..

---

How come wrong numbers are never busy?
[HD2 Android NAND Development] MarkAtHome:
I might not be recalling correctly, but I think that it did happen to me, and

after rebooting

, all was as it was prior to the upgrade.

___________________

Sent from my HD2 ICS CM9 with XDA Premium
[HD2 Android NAND Development] NYLimited:
Nightly /weekly builds

Is there some place I can find out what change has taken place in the latest DB posting? Apologies if I missed the info...
[HD2 Android NAND Development] deckoff:
Trying to re-part my NAND. I have Ubuntu oly.

Tried to use the sd version/

So I downloded fiel 2 and 3.

Extracted conted of zip2 to root of SD card

Copied zip3 cwm zip itself to root, no extract. Added flash.cfg to zip 3.

When I booted to AD SD I got

SD Kernel open failed

Any ideas.

PS I want to repartition my NAND (enlarge system to 195) and dont know how to do it without NAND toolkit or flashinf CWM.zip with flash.cfg.
[HD2 Android NAND Development] SonicCube:
Dear All,

Is there a way to install update.zip on SD version Android? I want to install camera update to my HD2 ruuning ICS from SD. Thanks.
[HD2 Android NAND Development] Glen_H:
I need your help

As some of you might know is a low volume bug in the tytung's and maybe other ICS builds when using data2sd.

Clearing dalvik-cache from CWM before boot resolves this, but it means we have to rebuild dalvik-cache which takes a lot of time.

I found out hat manually removing dalvik-cache didn't resolve the bug, and clearing the dalvik-cache without sdcard inserted (dalvik-cache doesn't have to be rebuild at boot) did resolve the bug.

Clearly clear dalvik-cache is doing more than just removing the dalvik-cache folder but I don't know what. If any of you could tell me maybe we can solve the low volume bug.

Thanks
[HD2 Android NAND Development] Realalist:
I edit the Mic gain using root explorer, that has fixed the problem for me

Sent from my HD2 at the speed of light
[HD2 Android NAND Development] MarkAtHome:
Does anyone know exactly who is responsible for (and/or the author of) CWR? Koush? Arif-Ali? Cotulla?

I do have issues that I posted privately to the first two, and have not heard back (it has been quite sometime).

Is there a contact point that is actively monitored?
[HD2 Android NAND Development] arif-ali:
I am not the author of CWR, koush is.

seadersn and myself ported it to the HD2 in the form it is today, where raiderX initially ported it initially.

I do apologise, I have been extremely busy with big projects at work, and I do other development work other than XDA, and then I do have family life, and therefore I haven't been able to answer any questions in PM.

As I no longer have an HD2, I can no longer test any of the things you mention (I need to buy another one for development). I have moved onto SGSII, and soon I will start attempting Nexus 7.

With the nature of the CWR not being officially supported by koush, he doesn't need to reply and help. This is something we added and added support.

I have looked at the logs you provided, and there seemed to be an issue with files and filenames being appended to each other, hence assuming a filename to be really large, and therefore was not able to backup. Maybe you are exerting the phone to it's limit with memory; maybe try removing some of the large applications, and then trying the backup.

wrt the touch recovery, koush has not released the source code, and therefore I don't have any way of porting that over, so unfortunately, it is what it is.

regards,
[HD2 Android NAND Development] robertolm:
hellow,

Thanks for that great app or port this app.....

One question:

I had HD2 with a usb damaged....

I had installed MAGLDR 1.13 and had to boot from cwm from sd.

At begining I had the cwn 3.0.0.5 on nand and I can flash from nand cwm 3.0.0.5....

But I tried to install cwm 5.0.2.6.cwr and late ... doesn't start again the AD Recovery.

The normal install was:

1.task29

2.Flash radio

3.flash magldr 1.13

4.flash from Magldr with option 5.USB Flasher -> cwm from usb the image.img.

But i cann't use the USB port.....

Is posible to reflash cwm or repartition the NAND like when install cwm from other cwm booted from sd??????
[HD2 Android NAND Development] samsamuel:
i think there is a version of cLK that can be flashed from sd card, and i also believe you can repartition without usb when you use cLK. Ive never USED cLK so i cant verify this, but im sure ive seen it given as an answer a few times.
[HD2 Android NAND Development] MarkAtHome:
Ah. I knew that you were both involved but wasn't sure of the connection. Thanks for clarifying that.

You have no reason to apologize for having a life. I totally understand and appreciate that, Arif-Ali.

I figured that if you were involved with the code, you might be able to shed light on my issue. I was trying to keep it low key until I get a Nexus 7! ;)

Too bad that the lines of communication between you two wasn't better. If it was, ROM Manager would know about your latest ported versions, and in turn, Koush would be able to provide HD2 support for his touch recovery.

I was thinking along those lines. Do you know how CWR uses memory? Since it is being accessed before the ROM is launched, it has a definite amount of memory available to the TMO HD2 to create/restore recovery images. I have over 900 apps installed into an Ext4 SD-Ext partition of 8G (evaluation purposes).

So, I was thinking that CWR was possibly running out of memory during those routines, not anticipating a need for additional memory. If that was the case, I figured that you or Koush would be able to tell me if that was the issue...

Presuming that all of the above is true, and there is nothing to be done, can you point me toward an alternative recovery image to use instead of a CWR-based one?

Without one, I cannot do NAND backups or restores. :(
[HD2 Android NAND Development] NYLimited:
I certainly have not seen any alternatives. Have you looked at the iPhone? :banghead:

---

There are nights when the wolves are silent and only the moon howls... (via XDA app)
[HD2 Android NAND Development] MarkAtHome:
Keep doing that. :silly:
[HD2 Android NAND Development] NYLimited:
'tis an alternate reality...

---

There are nights when the wolves are silent and only the moon howls... (via XDA app)
[HD2 Android NAND Development] kokotas:
Hi,

I think it is possible to do a backup using the command line tools within Android system.

You need to have the required tools installed (busybox , dump_image , mkyaffs2image) ,

/sdcard & /sd-ext mounted and

enough free space on your sdcard to hold such a huge sd-ext backup .

Regards!

EDIT:

The following is an example of what I mean - NOT a tested script.

# Make it Nandroid style
cwm_backup_path="/sdcard/clockworkmod/backup"
cd $cwm_backup_path
my_backup=`busybox date -u +%Y-%m-%d.%H.%M.%S`
busybox mkdir -p $my_backup
cd $my_backup
# Backup boot
dump_image boot boot.img
# Backup recovery
dump_image recovery recovery.img
# Backup system
mkyaffs2image /system system.yaffs2.img
# Backup data
mkyaffs2image /data data.yaffs2.img
# Backup cache
mkyaffs2image /cache cache.yaffs2.img
# Backup .android_secure
busybox tar -cvf $cwm_backup_path/$my_backup/.android_secure.vfat.tar sdcard/.android_secure
# Backup sd-ext
ext_type=`busybox mount | busybox grep "ext" | busybox cut -d ' ' -f 5`
ext_mount=`busybox mount | busybox grep "ext" | busybox cut -d ' ' -f 3`
busybox tar -cvf $cwm_backup_path/$my_backup/sd-ext.$ext_type.tar $ext_mount
# Create md5sum
busybox md5sum .* * > nandroid.md5

EDIT2:

As I thought, it has been already done, so don't mind the above. I didn't try this, but I think it could work for you too.
[HD2 Android NAND Development] MarkAtHome:
Of course I will mind the above. I appreciate the effort you made in trying to help me. That's enough, and I will look into the thread you provided.

Thank you!

Any thoughts re TWRP 2.2.0?
[HD2 Android NAND Development] MarkAtHome:
I have subsequently discovered the answer.

FAT32 partition sizes is not an issue. FAT32 filesize is an issue.

Apparently, a FAT32 file cannot be greater than 4G. I have also been told that Linux looks at a FAT32 partition as vFAT, which has a 2G filesize limit.

The latter does not seem to hold true, in my case, since I have successfully created and restored NAND backups containing sd-ext.ext4.tar files just less than and greater than 4G, but no more.

Aside from my plight, consider that many more folks are purchasing 64G cards (as I have been using for a few months). While I have just looked, and can no longer quickly find it, when I last checked SanDisk (yesterday?), they had a graphic of their microSDHC/XC cards, including, all the way to the right of the graphic, a 128G microSDXC version. I was unable to find any mention of what I saw in that graphic.

The point being is that it might be time to either revise CWR to handle larger quantities and sizes of files for its backup, or look to something new.

Could be that if a ROM's kernel had NTFS support, we could use that filesystem instead of FAT32, and not run into the filesize limitation.
[HD2 Android NAND Development] NYLimited:
NTFS in Android is not likely to be addressed by CWM so it is a moot point.

The simpler solution, especially since an archive is being created, is a multi-part file. Zip and other like programs have been doing that for a long time (e. g. Multi part zips to fit CDs, etc.) The problem with this concept is the lack of backward compatibility, of course.

---

The reason I talk to myself is that I'm the only one whose answers I accept.. (via Tapatalk)
[HD2 Android NAND Development] MarkAtHome:
Might not be the case, as it is more kernel related than anything else. I am uncertain, but I vaguely recall Tytung indicating that NTFS was already kernel supported. Then again, I might have dreamt it...

I have also heard that Exfat might be a possibility.

As to your other suggestion, see TWRP 2.2.0. I have been in contact with the team, as those flashing it with an HD2, cannot boot past the green HTC logo (after MAGDLR).

I can confirm that.
[HD2 Android NAND Development] MarkAtHome:
While I am on an unsuccessful roll... :(

It appears that CWR has issues when the DATA partition is moved to an Ext4 SD-EXT partition.

When I choose Fix Permissions

or

Clear Dalvik, CWR's module runs and finishes in record time (almost immediately retains to the menu).

Fixing permissions via ROM Manager Pro (Koush) takes quite a few minutes as it scrolls through all the apps it sees (1000+, if I am reading it right), making corrections as needed. I can only conclude that ROM Manager does not have any issue with my DATA partition.

Clearing my dalvik cache via Titanium Backup Pro, actually finds files needing to be deleted. It prompts me, I answer affirmative, and it removes the files.

I am a bit surprised that this has not been mentioned before (I could have missed it in my search, so if so, I apologize) as a CWR issue needing to be addressed.
[HD2 Android NAND Development] ameer1234567890:
The reason for this huge time variance is because CWR runs in recovery and ROM Manager runs within android. When it runs within android, sd-ext partition is already mounted on a place in data partition. So the system will think that sd-ext partition is actually a part of data partition and act accordingly. But in recovery, since it is not mounted, system will see sd-ext as a separate partition.
[HD2 Android NAND Development] MarkAtHome:
I have been running CWR for somewhere around 18 months, give or take, and never had an issue with it clearing dalvik or fixing permissions, back then.

Subsequently, moving the complete DATA (with dalvik) partition to SD-EXT, I do not believe (based solely on viewing it), that it fixes permissions or clears dalvik. I've seen it spend a bit more time on it in the past, and if anything, it should be taking longer due to the amassed apps.
[HD2 Android NAND Development] NYLimited:
CWR should be able to fix permissions on system partition but likely not on data.

Wipe Dalvik has issues as I noted some time back. While in recovery, check logs immediately after attempting to wipe Dalvik and you will see the failures.

---

The reason I talk to myself is that I'm the only one whose answers I accept.. (via Tapatalk)
[HD2 Android NAND Development] kaiserlein:
TWRP 2.2.0 doesn't boot but the last version did (don't recall the version number).

Try the attached recovery.img. It's running fine on my phone.
[HD2 Android NAND Development] MarkAtHome:
Thanks, kaiserlein. I think that I have the previous version here somewhere, but will grab yours as well. Appreciate it.

Edit: I just wanted to let you know that it installed and it looks like I have a successful backup. The log concerns me, but I'll leave that for another day. Thanks again for your help.

120727 Update: Well, while the backup might have worked, dees_troy reminded me that I need v2.2 to resolve my issue of the FAT32 filesize limit -- v2.2 splits archives.

dees_troy no longer has an HD2, so that is a problem. Any idea how we will can get v2.2 to work for us?
[HD2 Android NAND Development] ph03n!x:
If clockworkmod fix permissions is getting completed in a second or less, look up the CWM log- you might be in for surprise.

Swyped from my HTC HD2 using XDA Premium
[HD2 Android NAND Development] MarkAtHome:
What a tease! :)
[HD2 Android NAND Development] ph03n!x:
:D Who doesn't like some suspense, and some fun!

Anyways, if you bumped into /sbin/fix_permissions: line 64: UID readonly variable in CWM log after fix permissions, here is the fix.
[HD2 Android NAND Development] MarkAtHome:
I'm getting too old for suspense, ph03n!x. That's an interesting find, for sure. Thanks.
[HD2 Android NAND Development] NYLimited:
Considering this is the last day of July I cannot help but agree.. :o

---

The reason I talk to myself is that I'm the only one whose answers I accept.. (via Tapatalk)
[HD2 Android NAND Development] petbede:
Howdy?

Please can u upload ClockworkMod Recovery v5.5.0.4 01.JUL.2012?

Thanks.

PEACE!!!
[HD2 Android NAND Development] NYLimited:
This should be the Recovery flashable version:

https://www.dropbox.com/sh/xoio3dwcxwe25dj/vy1hy__m9w/5.5.0.4/recovery_5.5.0.4-20120701_leo_CWR.zip

---

The IQ and the life expectancy of the average American recently passed each other in opposite directions. (via XDA app)
[HD2 Android NAND Development] petbede:
Howdy?

Thanks. I also click the THANKS BUTTON.

PEACE!!!
[HD2 Android NAND Development] MarkAtHome:
I find that as long as I keep my SD-Ext's filesize in check, TWRP 2.1 works great -- backup/restore, various wipes, mounts etc. I prefer to use AROMA Filemanager, than TWRP's built-in File Manager, finding it superior.

Now all we need is for someone to help out Dees_Troy and Arif-Ali with getting v2.2 working (now 2.2.1.4). It looks like a major improvement in function and features, and splits archives to circumvent FAT32's filesize limit.

Interested in trying your hand at compiling for HD2? Try here. It is beyond me... :(