yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] zach.antre:
Thanks for this info... it would be nice such an editor to exist.

I also think that ClockWorkMod need new structure menu as well as some extra features (if possible)

I will post more detailed information later... I guess seadersn you know what to do and to what people give those suggestions.
[HD2 Android NAND Development] arif-ali:
All you need is reiserfs support in the kernel, everything else will work automatically. One option when you use menuconfig, just select reiserfs in the menus, and re-compile kernel.

i have just tested with my kernel, and the ROM, mounted it after creating the FS on my PC.

give it a go
[HD2 Android NAND Development] cmarti:
I am going back to MAGLDR, the cLK data problems and lack of tethering are too much for me.

Love this ROM. :)
[HD2 Android NAND Development] zach.antre:
This is how ClockWorkMod menu tree is now:

- reboot system now
- apply update from sdcard
-- Yes - Install /sdcard/update.zip
-- No
- wipe data/factory reset
-- Yes -- delete all user data
-- No
- wipe cache partition
-- Yes - Wipe Cache
-- No
- install zip from sdcard
-- apply /sdcard/update.zip
--- Yes - Install /sdcard/update.zip
--- No
-- choose zip from sdcard
--- (Browse SD)
-- toggle signature verification
-- toggle script asserts
- backup and restore
-- Backup
-- Restore
--- (image to restore)
-- Advanced Restore
--- (image to restore)
---- Restore boot
---- Restore system
---- Restore data
---- Restore cache
---- Restore sd-ext
- mounts and storage
-- mount|unmount /cache
-- mount|unmount /data
-- mount|unmount /sdcard
-- mount|unmount /system
-- mount|unmount /sd-ext
-- format /boot
--- Yes - Format
--- No
-- format /cache
--- Yes - Format
--- No
-- format /data
--- Yes - Format
--- No
-- format /misc
--- Yes - Format
--- No
-- format /recovery
--- Yes - Format
--- No
-- format /sdcard
--- Yes - Format
--- No
-- format /system
--- Yes - Format
--- No
-- format /sd-ext
--- Yes - Format
--- No
-- mount USB storage
--- unmount
- advance
-- Reboot Recovery
-- Wipe Dalvik Cache
--- Yes - Wipe Dalvik Cache
--- No
-- Wipe Battery Stats
--- Yes - Wipe Battery Stats
--- No
-- Report Error
-- Key Test
-- Partition SD Card
--- 128M
--- 256M
--- 512M
--- 1024M
--- 2048M
--- 4096M
-- Fix Permitions
- power off

And here is my suggestion:

- Install from SD
-- Apply "update.zip" from SD Card
--- Yes - Apply /sdcard/update.zip
--- No
-- Install zip from sdcard
--- (Browse SD)
- Mount
-- mount|unmount /cache
-- mount|unmount /data
-- mount|unmount /sdcard
-- mount|unmount /system
-- mount|unmount /sd-ext
-- mount|[COLOR=RoyalBlue]unmount[/COLOR] USB storage
- Wipe Partitions
-- Wipe Battery Stats
--- Yes - Wipe Battery Stats
--- No
-- Wipe Dalvik Cache
--- Yes - Wipe Dalvik Cache
--- No
-- Format /boot
--- Yes - Format
--- No
-- Format /cache
--- Yes - Format
--- No
-- Format /data
--- Yes - Format
--- No
-- Format /misc
--- Yes - Format
--- No
-- Format /recovery
--- Yes - Format
--- No
-- Format /sdcard
--- Yes - Format
--- No
-- Format /system
--- Yes - Format
--- No
-- Format /sd-ext
--- Yes - Format
--- No
- Backup
- Restore
-- (image to restore)
--- [COLOR=RoyalBlue]Restore All[/COLOR]
--- Restore /boot
--- [COLOR=RoyalBlue]Restore /recovery[/COLOR]
--- Restore /system
--- Restore /data
--- Restore /cache
--- Restore /sd-ext
- Advance
-- Fix Permitions
-- Key Test
-- Partition SD Card
--- 128M
--- 256M
--- 512M
--- 1024M
--- 2048M
--- 4096M
-- Report Error
-- Toggle signature verification
-- Toggle script asserts
- Power Options
-- Reboot ClockWorkMod Recovery
-- [COLOR=RoyalBlue]Reboot to Bootloader[/COLOR]
-- Reboot System
-- Shut Down

In blue is what should be added (if possible)

The menu tree is different for better use.

A little cleanup (doubles have been removed)

It's just a suggestion to the developers of CWM, if it's too much trouble just let it be... :)
[HD2 Android NAND Development] jackielo:
MAGLDR_recovery_3.0.2.4.zip is broken. Somebody can send me a working one? Tks.
[HD2 Android NAND Development] UbuntuBhoy:
Can I ask a daft question, the flashable cLK zip, where does it get flashed from?
[HD2 Android NAND Development] seadersn:
zach.antre: don't expect too much from me and/or "my connections" ;) i'm already working on getting deeper into this stuff: what sometime will result from that is another point and unclear until now. anyway: thanks for your efforts and recommendations and examples :) the clockwork menu can be rearranged, sure, menupoints removed etc. what would be interesting: advanced backup of only single partitions :)

@ arif & pongster: the sd-ext mounting in cwm is set to auto (not ext2-4 in special), so i believe too that this will be sufficient for being able to handle these "special filesystems" inside cwm and that the kernel with which cwm was compiled will affect / define this. maybe next version may include it, needs testing :) i will compile a testversion, which one can test; maybe tomorrows evening, as i'm really busy this weekend (gf, rl in general, especially parents etc; there's much to talk about future atm).

you can flash the flashable zip from for example an existing 3.0.1.9 / 3.0.1.4 recovery to easy update it ;)

and what's up with the magldr zip you've mentioned, jack? for me the download works and is ok?
[HD2 Android NAND Development] UbuntuBhoy:
Thanx for the reply, it just seemed weird to flash the update from CWM itself.
[HD2 Android NAND Development] seadersn:
i didn't test this for myself until now :) it should work, because cwm operates from RAM from what i've read sometime; but i am not completely sure.
[HD2 Android NAND Development] arif-ali:
here's a test version, that I have been using for the last few days

recovery.img.zip (cLK only) not sure if this will work with MAGLDR

kernel_aa_0.5_test.zip

And I'm currently running using reiserfs, and all seems to work well.
[HD2 Android NAND Development] seadersn:
k, will test it when some time is available; full saturday here... :(

if boot is MTD and not YAFFS2 in recovery.fstab, then it will not work on magldr.
[HD2 Android NAND Development] billycrf100:
My usb port has broken on my hd2 and the last version of cwr I flashed was with the 400mb system partition. This means I can only flash a few roms that give me more than 7mb of internal storage. If I flash the SD version of cwr, will it let me recover any custom Rom again? If this doesn't work then my cwr will be gone so that's why im checking first.
[HD2 Android NAND Development] zach.antre:
You have an alternative.

Keep CWM as is right now and partition your SD with CWM, it will create an ext3/4 partition which will actually store all data.

In your phone it will say 7mb of internal storage but infact you have exactly the size you have partitioned. So for example if you choose to partition 1000MB, you will have 1GB to install app (even though it will continue say 7mb)

Of course assuming that a2sd/a2sd+/data2sd is implemented in the rom you want to use.

That way you can flash any ROM you like in the future (Sense, nonSense etc) and you will have plenty of space for apps.

---------EDIT-------------

I have just noticed that with CWM SD version you can only run CWM and thats all, no partitioning.

So you have to do the SD partitioning solution.
[HD2 Android NAND Development] pc332412258:
Thank you for sharing, like very much,it's nice
[HD2 Android NAND Development] pongster:
the kernel I use supports Reiser, does this mean this version of recovery will support backing up and restoring a reiser sd-ext? or will seadersn 3.0.2.4 version work as I already have Reiser support enabled in the kernel?
[HD2 Android NAND Development] seadersn:
i believe i have to compile it with a kernel, which supports reiser etc, then you can use it :-) will do it todays evening, when i'm at home again, that will be roundabout 20:00 gmt+1.
[HD2 Android NAND Development] billycrf100:
Thankyou but this way wont allow me to install any apps that are more than 7mb
[HD2 Android NAND Development] seadersn:
then you'll need an initrd.gz, which is linking cache into data partition ;)
[HD2 Android NAND Development] arif-ali:
Yes that's right your rom should work. The recovery I have posted as a kernel with reiserfs support. So should work.
[HD2 Android NAND Development] pongster:
Nice. What's your verdict re: reiser performance on android so far? :)

Sent from my HD2 powered by HyperDroidGBX
[HD2 Android NAND Development] arif-ali:
Personally, I've been pretty impressed. But maybe some continues testing may be required.
[HD2 Android NAND Development] pongster:
Nice. I figure reiser would perform well in Android, given that we deal with a lot of small files that the system accesses to run... reiser seems to fit the bill in that regard.

Will be updating my sdext today to test the recovery img you posted... does it include the edits of erasers as well? And were you able to restore an backed up sdext formatted as ext4 to the new reiser sdext?

Sent from my HD2 powered by HyperDroidGBX
[HD2 Android NAND Development] arif-ali:
you mean seadersn,

The recovery I use has the yesno patch, but the no is first and not second, it has the cLK patch from cedesmith, sd-ext mount, and the kernel I compiled for reiserfs support.

afaik, I was able to restore without any problems, but I can't remember, as I re-flashed later. I will test that again, will confirm
[HD2 Android NAND Development] GanJiMan:
That didn't work for me - says Invalid file size or something. Guess it is because the new version is bigger than the previous one. Any advice on how to partition the ROM when flashing so it is future-proof? :)
[HD2 Android NAND Development] seadersn:
recovery partition size of 5M should be good size, even for future releases. :)
[HD2 Android NAND Development] karendar:
Hey Arif, is there anything special that needs to be done to use ReiserFS in clockwork with your recovery.img? I flashed recovery, formatted my SD to reiserfs with 128 meg swap, but it says cannot mount sd-ext.
[HD2 Android NAND Development] arif-ali:
Make sure that the raisers partition is the second one. i.e the following layout

1. vfat

2. reiserfs

3. swap
[HD2 Android NAND Development] MaXAiRO:
Could someone please post a 3.0.2.4 Recovery with 10M Cache instead of 5? I cannot download apps from market that are more than 4MB in size.
[HD2 Android NAND Development] arif-ali:
If you are using MAGLDR, then you need to change the flash.cfg, and flash.

If you are using cLK, it is nothing to do with the recovery, it is in-fact to do with cLK, and you need to compile cLK with the correct values.

There is now a howto, on compiling cLK, check my signature
[HD2 Android NAND Development] MaXAiRO:
Doesn't it have to do with the CWM Recovery? I think that I started having the problem when I flashed 3.0.2.4 Recovery. It was all ok with the 3.0.1.9 provided in Tyween's ROM first post.
[HD2 Android NAND Development] D.O.C:
I did exactly that, sdext wont be recognized... it is recognized by pongster's mod ty8.3 kernel on gbxv11 and cm71.0.4, only cwm does not... sorry
[HD2 Android NAND Development] seadersn:
@ max:

@ cete: let's do some trial-sessions on this, today or tomorrow :) we'll figure this out, i believe.
[HD2 Android NAND Development] Unconn:
I have a strange one. Does this CWM use the directory name in the calculation of the MD5? I know other versions I have used do not. This week I have been doing loads of backups. Well, last night I had to roll back. Backups where I did not rename the directory restored fine. Ones that were made with a different version of CWM also did. Ones where I had renamed the directory failed MD5 check. I was able to take my tag off the end (-CM7-cookname) and it restored fine.

Seadersn, does it use the directory name in the calculation of the MD5?
[HD2 Android NAND Development] karendar:
That's already the case... FAT32 primary, 1.2gb reiserfs, 128mb swap (Linux-swap?)

I'll do some more testing.

--------

After doing a little more digging, CM7 Hyperdroid 1.0.4 with cLK kernel detects the reiserfs partition perfectly, works great. When booting in Arif's Clockwork, sd-ext isn't mounted anywhere. When trying to manually mount mmcblkp0p2, it gives an error saying the device doesn't exist. I used the following command:

mount -t reiserfs /dev/block/mmcblk0p2 /sd-ext/

Is this correct? Because it gives an error. CWM doesn't detect partition 2 even though I made sure in gparted it's all properly partitionned. This is what the mount point in CM7 looks like:

/dev/block/mmcblk0p2 on /sd-ext type reiserfs (rw,noatime,nodiratime)
[HD2 Android NAND Development] karendar:
I rename folders all the time and MD5 stays fine. You can always recreate MD5 after rename using:

adb shell

# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53

# rm nandroid.md5

# md5sum *img > nandroid.md5
[HD2 Android NAND Development] Unconn:
I might have something else wrong then. Never had this before. I have always renamed them from something like 2010-06-29.20.22.53 to 2010-06-29.20.22.53-CM7-5.8.1-Cook. This is the first time I have had the MD5 fail or hang. I renamed them back, but this also included rebooting, so it could be something else that fixed it.

If I get it again I will try recreating the MD5 and see if that helps.
[HD2 Android NAND Development] bhagiratha:
Hi

I am stuck at clockworkMod recovery v3.0.0.5, and would like to upgrade to the latest version.

How do I do that? About to update to HyperDroidGBX-v11

When I unzip "MAGLDR_recovery_3.0.2.4.zip", I get a "MAGLDR_recovery_3.0.2.4.img" file.

what do I do with this .img file?

thanks
[HD2 Android NAND Development] seadersn:
birkoffsjunk created a cwm flashable zip; you can find it linked in first post and try it :-)
[HD2 Android NAND Development] bhagiratha:
I found that zip file, but how to I apply it ?
[HD2 Android NAND Development] seadersn:
for me it reads that you have 3.0.0.5 already installed? if yes, boot into it and flash it with "install zip from sdcard".

if not, you can copy the files of sdcard version to your card, boot this up and flash from there; i believe... :D i didn't test this ;) please report if this worked!
[HD2 Android NAND Development] bhagiratha:
I tested on my phone, but got this error message ....
[HD2 Android NAND Development] seadersn:
you can try to copy the img file on your sdcard, rename it to recovery.img and then run

su

flash_image recovery recovery.img

in terminal emulator. otherwise you have to reflash new partition layout with this recovery file within usb flasher menu of magldr, as described in first post :(

you are on magldr?
[HD2 Android NAND Development] bhagiratha:
Yes, I am on Magldr.
[HD2 Android NAND Development] seadersn:
have a look at this: :)
[HD2 Android NAND Development] bhagiratha:
Thank you for the suggestion. I tried according with your instructions, but got this message from within connectbot:

flash_image not found

Is there some other file I am missing on my sdcard?
[HD2 Android NAND Development] seadersn:
you can try it with the one which is attached; unzip it, copy it over into /system/bin folder and type in terminal emulator / connectbot:

su
chown 0.2000 /system/bin/flash_image
chmod 755 /system/bin/flash_image

:)
[HD2 Android NAND Development] bhagiratha:
Got this error message ....
[HD2 Android NAND Development] seadersn:
your recovery partition is too small :( you can flash a new layout with fixed recovery partition size of 5MB or wait for the new version, which may be smaller (i hope).
[HD2 Android NAND Development] lorezz:
i would like to update to cwm 3.0.24....but after many attempts no succes....

adb doesn't recognize my phone....why?
[HD2 Android NAND Development] arif-ali:
are you using linux or windows?

for linux, try running adb as root

for windows, you need the drivers for adb, to get working. have you tried getting the relevant drivers, The following link has the relevant drivers

http://www.multiupload.com/9R0KMRJ5X0
[HD2 Android NAND Development] lorezz:
done....it was my fault because i made a mistake with some directory....bytheway thanks for the help....
[HD2 Android NAND Development] randasecret:
guys ,

how to compile CWM from source on ubuntu

thanks
[HD2 Android NAND Development] seadersn:
build up environment for leo, then 'make recoveryimage'. :)
[HD2 Android NAND Development] arif-ali:
The following will grab the whole of cyanogenmod, which will have the relevant details

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync

Then run the following commands

Change anything in device/htc/leo, and bootable/recovery folders, as required

cp ./vendor/cyanogen/products/cyanogen_leo.mk ./buildspec.mk
. build/envsetup.sh
lunch cyanogen_leo-eng
make recoveryimage

You will now have the recovery.img in out/target/product/leo/recovery.img

I hope that helps

Will have a detailed Howto soon
[HD2 Android NAND Development] seadersn:
arif, our howto-man :D ;) thx!
[HD2 Android NAND Development] randasecret:
thanks arif and seadersn
[HD2 Android NAND Development] zach.antre:
I am using the latest, updated on April 12th, CWM 3.0.2.4 and i have noticed that when i plug in the usb (connected to pc) when phone if off (for charging) it makes a noise... is that normal?

I haven't noticed if that is also happens in older versions of CWM.
[HD2 Android NAND Development] seadersn:
holla... i have to test this as my windoze sounds are all switched off; i think it's windoze which's making a sound...? can't believe that it's the phone, because here it's silent :D

maybe this is caused by recent changes @ cm-team regarding charging for htc devices; but i will test the "sound issue" first here on my pc.
[HD2 Android NAND Development] seadersn:
recovery updated, both magldr and cLK version.
[HD2 Android NAND Development] THANHVO31:
Sorry for my noob question: is there any way flash via CWM difference layout like 90M/120M/135M/150M/250M/400M without plug in to a PC? As flashoholics, we need to change those layout back and forth daily and it will save a lot of time!
[HD2 Android NAND Development] crysanthus:
+1

me too :-)
[HD2 Android NAND Development] seadersn:
nope, unfortunately not. partitions are normally of fix size in every normal phone, we can be happy to be able to change the sizes ;) but cwm isn't responsible for and able to do that.
[HD2 Android NAND Development] K_Hismoom:
Thanks for the new version.

Unfortunately the MAGLDR version doesn't seem to work on my device, it's stuck on GO GO GO.

I already did a task29, reinstalled MAGLDR and CWM numerous times, but it won't work, I also tried different partition layouts without luck. When flashing 3.0.0.5 from the thread you link to (the one with the layout files), that version works.

Is there any way you could upload 3.0.1.9 version? Because that one worked beautifully, but I don't have the files any more.

The cLK version does work though, but I'd like to stay with MAGLDR.

Any ideas there?
[HD2 Android NAND Development] hg3atintin:
+1 same problem here.
[HD2 Android NAND Development] tytung:
Yes, MAGLDR CWM 3.0.2.4 (Apr 13) version stuck on GO GO GO when using AD Recovery.

SD MAGLDR CWM 3.0.2.4 (Apr 13) version has no problem.

You can use MAGLDR CWM 3.0.2.4 (Mar 25) version before Seadersn solve it.

Download http://nexus-hd2.googlecode.com/files/CWM_Recovery_v3.0.2.4_for_NexusHD2_135M.zip

What you need is MAGLDR_recovery_3.0.2.4.img.
[HD2 Android NAND Development] clyder:
I also have the stuck at gogogo with new 3.0.2.4 magldr version. Reverted to old 3.0.2.4 and it went fine.
[HD2 Android NAND Development] jigners:
great work! but this will prove a challenge for the vast newbies here. difficulty

rating = escape from "al catraz":) but am certain as this evolves it will become

more straight forward.

tbh, why complicate things? let MAGLDR be as it is, unless it has developed

serious problems - which i very much doubt. and let cLk be as it is.

its all a matter of choice which method will people be comfortable with.
[HD2 Android NAND Development] OCedHrt:
Did anyone actually test cLK off-mode charging? I am using cLK 1.4 with recovery 3.0.2.4 and tytung9 and it still boots into Android when I plug in the USB cable.

Update: Issue with my non CLK ROM. Flashed to CLK version and it's working now.
[HD2 Android NAND Development] arif-ali:
off-mode charging does work for me.
[HD2 Android NAND Development] OCedHrt:
Issue with my non cLK ROM. Flashed to cLK version and it's working now. I just changed the boot loader and kernel and restored a non cLK rom.
[HD2 Android NAND Development] THANHVO31:
OK, anyway just Task29+Radio > Magldr> CWM 3.0.xxx !:D

By the way, could you explain me Layout scheme of some build:

Normal 150M

misc ya 1M

recovery rrecov|ro|nospr filesize recovery-raw.img

boot yboot|ro 5M

system ya 150M

cache ya 44M

userdata ya|asize|hr allsize

Or in short standard 1-5-150-44

But the other like GBX 1-5-120-10

Nexus HD2 1-5-135-5

dillapse 1-5-80-40

My question is cache partition why so vary among build? If more than enough just waste remain space but use small version can make build FC?

Thank in advance.
[HD2 Android NAND Development] tytung:
Nexus HD2 1-5-135-2

Cache partition is only used by CWM.

My ROM will use data partition to save the cache files.

/cache is pointer to /data/cache

/cache/recovery is pointer to /data/cache/recovery

So if my remaining data partition has 180MB, then my cache space has 180MB too.

Cache space is used by Market downloads.
[HD2 Android NAND Development] zach.antre:
Wow... cool new feature :D

Now we can flash CWM from our android device, wherever we are...

It would be nice though if bootloader(s) were fused with CWM so we could just flash everything from our device (leoimg.nbh - not recomended). I guess Cedesmith is working on it... :)
[HD2 Android NAND Development] seadersn:
hoi, much questions, and unfortunately negative messages for magldr version :( i'll try sth to solve this, but can anyone test a partition size of "5M" for recovery instead "filesize" tag?

@ than: your question is answered by tytung...? let me know :)

tytung, thanks for providing the link to your layout whic is using the older recovery version ;) i'll upload this version until the problem is solved.

i don't use magldr anymore; is there someone who can assist me with testing the new recovery i will have compiled todays evening or tomorrow? i want to test it before i release it, but are not willing to change back to magldr ;) sry :D i just don't want to see the magldr menu anymore...
[HD2 Android NAND Development] seadersn:
k, uploaded old version for magldr nand.

but i don't understand why it's working from sd and not from nand; nothing has changed from my point of view which is causing it.

would be nice if someone who already downloaded new version from today could test the changre from "filesize" to "5M" in flash.cfg.
[HD2 Android NAND Development] tytung:
Changing from "filesize" to "5M" in flash.cfg doesn't work.

I rebuild a MAGLDR_recovery_3.0.2.4.img from the zImage and initrd.gz in magldr_sd_recovery.zip (Apr. 13 version) and it works now. (work for "filesize" and "5M")

./mkbootimg --base 0x11800000 --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk initrd.gz -o MAGLDR_recovery_3.0.2.4.img

Download MAGLDR_CWM_Recovery_v3.0.2.4_for_NexusHD2_135M.zip

From my observation, your previous magldr_recovery.img seems to be lack of --base 0x11800000 parameter.

I remember I don't see 0x11800000 when the phone stuck on GO GO GO using AD Recovery.
[HD2 Android NAND Development] birkoffsjunk:
Here is an updated ClockworkMod Recovery 3.0.2.4 (cLK) as a flashable zip :D
[HD2 Android NAND Development] metko:
how to upgrade from he older version (MAGLDR)
[HD2 Android NAND Development] seadersn:
ahh... thx for pointing this out, i will have a look at BoardConfig.mk. :) ok, thank you tytung; i will correct this ;)

expect a new magldr version in ca. 3 to 4 hours :) or i simply use yours, if it's ok for you? :D no need for recompiling.
[HD2 Android NAND Development] seadersn:
use flash_image ;) have a lok at first post.
[HD2 Android NAND Development] tytung:
I'm tytung, not tyween. :)

You only need to use mkbootimg command or use my created .img directly.

No need for recompiling.