yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] pongster:
yes it doesn't mount it :)

can you post your script for testing here?

so you used arif's script + your edited 99complete and it works without replacing your cLK CWM right?
[HD2 Android NAND Development] seadersn:
nope, i've deleted arif's script and only edited the 99complete :)

here is what i've putten inside:

mkdir /data/cache2
mount /dev/block/mtdblock4 /data/cache2
mount -o bind /data/cache2/recovery /cache/recovery

maybe i'll change this mountpoint, but basically it's of no matter where it's located, so why change it.

and yes, it's working without replacing it now :)
[HD2 Android NAND Development] wolfpack612:
not sure why it didn't work for you.

-i created an empty file "02cache"

-copied over arif's script

-saved my file

-pushed the file to /system/etc/init.d using adb

-changed permission and ownership using adb shell

-rebooted my hd2

i love how i can now go into rom manager, touch backup my rom, and it reboots into recovery automatically, backs up my rom, and then reboots back into android on it's own. AWESOME!!!

before when i would backup my rom i would sometimes forget and leave my phone there waiting. don't have to worry about that anymore :D
[HD2 Android NAND Development] seadersn:
jep, this and the possibility of deactivating the progress bar in the settings of rom manager :) this lets the backups/restorings take roundabout 40% less time for doing their jobs. go into settings of rom manager and check "quick backup and restore"; it's

very

fast then!
[HD2 Android NAND Development] pongster:
Noob question here... :)

How do you setup RomManager? DO I choose to install/flash CWM to enable backing up? What phone model do I confirm and won't this replace the cLK CWM mod you made?
[HD2 Android NAND Development] JDM Civic EG8:
I tested the kernel from this link for 2 different builds just to see what would happen

Hyperdroidgbx 9v loads and everything but soon as you select wifi it bootloops

UD 3.1.1v2 it loads up also but same thing bootloop
[HD2 Android NAND Development] pongster:
the wifi driver in Raf's kernel is not the one from AOSP so the wpa_supplicant needs to be replaced as well.
[HD2 Android NAND Development] JDM Civic EG8:
ohhhh that would make alot of sense haha thanks bro btw idk if this was asked in here or not but to flash your hyperdroid which kernel would i need?
[HD2 Android NAND Development] pongster:
I flashed cwm from rom manager (as I couldn't use any of the functions without doing so) and selected Nexus One... it flashed it (it said it did) then I reboot only to find out my cLK install has been wiped! :D

I could still boot the ROM but no access to Recovery or fastboot at all...

any ideas on how to get RomManager to work properly? clk_CWM by seaders was installed first... if that should matter...
[HD2 Android NAND Development] pongster:
v5... (its gonna be v6 soon as I added the patch to support reboot to recovery) :)
[HD2 Android NAND Development] JDM Civic EG8:
sweeet thanks alot bro I truely appreciate it. I can just wait until the v6 comes out haha. Ive tried out your MAGLDR cwm version and its the fastest build. But like being able to charge my phone while its off so switched to cLK
[HD2 Android NAND Development] arif-ali:
I used the Desire HD device, and it didn't replace my clk, so all was good for me. But since then I have replaced my clk with 5M cache and restored the same rom, on which I had already chosen the device, so was working straight away.

For those people having problems with the script, I will have another look at it today, and see what I can do to fix it

Edit: OK, I have tested it in terms on when it is a directory and not mounted, and I have tested this on my device and it seems to work.

@seadersn, could you give me your errors, or the diagnosis, that I requested from karender yesterday, so that I can see where it was going wrong. it would be useful for you to run

sh -x 02cache

this will give me a trace of exactly what is happening with the script.
[HD2 Android NAND Development] ironheart:
I tried the script Arif-Ali kindly provided. I got the following issues:

- 02cache (in /system/etc/init.d) is not executed (permissions set)

- i manually altered the 99complete:

# Mount NAND-cache partition

mount -o rw,remount rootfs /

mkdir /mnt/cache

mount -t yaffs2 -o rw /dev/block/mtdblock4 /mnt/cache

ln -s /mnt/cache/recovery /cache/recovery

mount -o ro,remount rootfs /​

"/cache" is symlinked to "/data/cachemnt" in my build, so by now there is a symlink "/data/cachemnt/recovery" which links to "/mnt/cache/recovery".

EDIT:

RomManager is installed, but i get a "ClockWorkMod Recovery unknown" message. Also i noticed that when i try to "reboot to CWM" in RomManager the device reboots to mormal system instead of recovery-mode. When i try to install a CWM in RomManager (my only choice: HTC Desire which gives me CWM v 2.5.0.7) it destroys Seadersn's CWM (no reboot to recovery possible anymore - "bad boot header").

OK, i reflashed the recovery partition with Seadersn's CWM and ROM-Manager still shows CWM v 2.5.0.7. ROM-Manager seems to be functional theoretically (reboot into CWM / backup existing ROM) but still reboots to normal system. Any suggestions?

EDIT2:

I FINALLY GOT IT WORKING!!

02cache didn't work out for me so I altered the "99complete"-script. This is what I've done:

# Mount NAND-cache partition

mount -o rw,remount rootfs /

rm /cache

rm -rf /data/cachemnt

mkdir /cache

mount -t yaffs2 -o rw /dev/block/mtdblock4 /cache

chown 1000.2001 /cache

if [ ! -d /cache/recovery ] ; then

mkdir /cache/recovery

fi

chown 1000.2001 /cache/recovery

chmod 0770 /cache/recovery

mount -o ro,remount rootfs /​

I think the crucial point is to mount the NAND-cache-partition to the "/cache"-FOLDER (symlinking didn't work for me!). After that everything worked fine including rebooting from Rom-Manager to recovery (v2.5.0.7) and automated backup from Rom-Manager!

Great job done, Arif-Ali! Thanks again!!
[HD2 Android NAND Development] arif-ali:
@ironheart,

The only problem with what you have done is that any big downloads via the market will not work if you have cache at 5M, and if you are using the cache at 20M, then your process will work without any problems.

Do you have the list of errors that you got?

btw, I have updated the script again
[HD2 Android NAND Development] ironheart:
Arif-Ali, one more question:

You said, that it was possible to install the RomManager-CWM for Desire-HD (v3.0.0.5). Is it possible to manually install the CWM for DesireHD, because I'm only able to select HTC Desire in Rom-Manager.

I downloaded the DHD-CWM from the author's page - gives me an ".img"
[HD2 Android NAND Development] ironheart:
I already thought about that (issue with market-downloads) - probably I'm going to change the cache-partition size.

EDIT: ok, going to take a look on your new script.
[HD2 Android NAND Development] arif-ali:
we only had to do that to get the rom manager to work, as it wouldn't let me use it. But then I went back to 3.0.1.4, which you should be able to get from seadersn's thread
[HD2 Android NAND Development] ironheart:
Yes, I already did that but now I have TWO CWMs. Seadersn's CWM (v3.0.1.4 v2) is starts normally by "rebooting to recovery" (out of system or via cLK). Rom-Manager's CWM (v2.5.0.7) is started also normally by selecting "reboot to recovery" or "backup rom" out of Rom-Manager. Seems that Rom-Manager's CWM is booting from an image or something like that. Weird.
[HD2 Android NAND Development] bhilgeman:
It probably downloaded an update.zip file to your sd card and is loading that.
[HD2 Android NAND Development] ironheart:
Yes I think so too... btw there's a "recovery-update.zip" in "/sdcard/clockworkmod/" which is also loaded by the Rom-manager.
[HD2 Android NAND Development] Dasf77:
Do you think that with the ability of rebooting into recovery, would it be possible to get OTA updates for your rom's in a near future?

I also have an Htc Desire an it has that choice.
[HD2 Android NAND Development] pongster:
That takes more work then it looks, believe me. But I'm looking into it. Not a top priority, but a possibility once we can sort out rommanager and clk cwm by seaders :)

Sent from my HD2 powered by HyperDroidGBX
[HD2 Android NAND Development] Satyan:
Data Abort with clk 132

- HSPL 2.08 , Radio 2.14.50.02

- I have tried clk 132 from the 1st post .. Data abort..

- tried building from source. .. Data abort..

- did task29, flashed original ROM.

- Flashed again. .. same problem.

- Changed to HSPL 3.0.3 Radio 2.15.50.02

- flashed again, Same problem ..

- There is no problems on 1.3.1

this occurs on Recovery/fastboot / wont flash after this...device is hung..

attached is the screenshot.
[HD2 Android NAND Development] Dasf77:
One step at the time. :D
[HD2 Android NAND Development] bhilgeman:
I flashed your hyperkernel 6 to use with Typhoon 2.7 and it just hangs at the HTC splash screen, is it not meant to work with Typhoon and clk?
[HD2 Android NAND Development] karendar:
Seems to be doing the same even for HyperDroid GBX ROM...
[HD2 Android NAND Development] pongster:
Its not for cLK yet... most users are on MAGLDR so that's the first one out... check the thread again and the cLK zip for CWM is ready for you. :)
[HD2 Android NAND Development] karendar:
Explains alot, I was expecting v6 to just be for cLK recovery update... ;) Flashing now!
[HD2 Android NAND Development] ironheart:
I checked your updated script (ref44) and it successfully mounted the cache-partition to "/data/cachemnt/" or "/cache/recovery" to "/data/cachemnt/recovery" respectively (in my case) but this rendered Rom-Manager-functionality useless and gave me other issues:

* "boot to recovery" / "backup rom" in RomManager keeps rebooting to normal system

* "reboot recovery" in system keeps rebooting to normal system

* "reboot recovery" in CWM keeps rebooting to normal system

I think mounting cache-partition to "/cache" is mandatory.
[HD2 Android NAND Development] Satyan:
Can somebody help me with this ...

thanks
[HD2 Android NAND Development] seadersn:
hmm, i didn't see these messages only one time...? so:

- you are flashing everything what is needed (requirements seem to be fulfilled (radio, hspl etc))

- then cLK 1.3.2 from first post, followed by recovery

- and then the errors occur...? if not, then

- boot into recovery and flash a zip of your choice, take pongsters hyperdroid for example and

- flash a kernel, which supports the new features, then

- wipe data / factory reset in cwm for formatting the data partition and

- the errors still occur...?

and regarding rom manager: IF it's flashing another recovery version, then simply reflash one of the recovery images which is offered in first and second post and patched for cLK 1.3.2, straight after reboot, caused by rom manager: go into fastboot and flash it. rom manager "has to believe" that recovery 3.0.0.6 from desire hd is installed, otherwise it wouldn't work, i believe :( 2.5.x.x from desire e.g. has the amend scripting, not edify, and therefore it wouldn't work i believe.

arif, do you need the error reports anymore? if yes, tell me and i will test it and pm you the logs you need.
[HD2 Android NAND Development] pongster:
So you select Desire HD then reboot into fastboot then install cLK_CWM and it should work? What'll it take to add HD2 as a device in ROM manager? anyone in contact with koush (Rom Manager dev)? I've read this so far... :)
[HD2 Android NAND Development] karendar:
Yeah, I read that too... Koush seems to always be willing to help get ROM manager on the most phones possible. ;) I'm sure he'd be more than happy to help get ROM manager certified HD2... Which would bring us one step closer to official Cyanogenmod support for our phone!
[HD2 Android NAND Development] karendar:
I just attempted to install ROM manager premium (For kicks) and then selected Desire HD to install the clockwork... It kept the 3.0.1.4 and I'm able to boot to recovery and backup ROMs with HyperKernel v6 straight from ROM manager. I'm trying all options and it seems to be going good. :D All that's left is to add the HD2 to the official ROM manager support list according to that link... And we have full ROM manager support. All that'll be left to do is get yourself working on OTA... haha!

Pongster, you really make my phone fun to play with. ;)
[HD2 Android NAND Development] pongster:
The ota should be easier then setting up the repository from where the downloads will be coming from and the scripts required to get it working. I'll talk to Tricalibur about that :D (and koush of course)
[HD2 Android NAND Development] kikisp:
i just can say: i love you guys :D
[HD2 Android NAND Development] karendar:
We love you too..? In a platonic kind of way. Yeah.

Moving right along! :D haha
[HD2 Android NAND Development] lippa:
I'm running standard version of rom manager.. Using hyper v6.. Selected desire hd and it detects 3.0.0.6 as being latest.. And its not working. Did you do anything special?
[HD2 Android NAND Development] seadersn:
IF it's flashing another recovery version, then simply reflash one of the recovery images which is offered in first and second post and patched for cLK 1.3.2, straight after reboot, caused by rom manager: go into fastboot and flash it.
[HD2 Android NAND Development] ironheart:
Could you upload a version without putting initrd.gz & zImage into the boot.img.

I want to create my own boot.img (with my own initrd.gz) so i need the patched kernel (zImage) from Rafpigna.

Thx.
[HD2 Android NAND Development] bhilgeman:
So reflash the one from this thread that was made for clk or fastboot flash the Clockwork recovery?

EDIT: Nevermind, i get what you're saying, when rom manager recourse the phone to go to recovery, fastboot flash the Clockwork recovery from this thread.
[HD2 Android NAND Development] wolfpack612:
did you guys notice that the screen is active during off charging? if I touch the screen it reboots. not sure if I overlooked that.
[HD2 Android NAND Development] bhilgeman:
For those getting ROM Manager to reboot into Recovery and accomplish a task, can you please give some details of what you did?

I'm using Typhoon 2.7.1 with Hyperkernel 6 for clk, and have the recovery from the OP for clk, and chose Desire HD from Rom Manager's list of devices.

When I use any of Rom Managers functions it just reboots back to the OS.
[HD2 Android NAND Development] Lucio25m:
How

Hi guys,

I really want to try this but I'm quite new and a bit lose.

I install the clk but after that I find my self in a dark hole.

Can someone point me out how to fastboot flash recovery.3.0.1.4_clk_1.3.2.img.

Sorry guys for the noob question

Thanks
[HD2 Android NAND Development] ironheart:
I got this issue too till i managed to mount the cache-partition DIRECTLY to "/cache" (in root!). Mounting the cache-partition to some other mountpoint (sd-ext or data ...) will render Rom-Manager useless for me (Rafpigna's DHD 4.0.1 build, DHD v1.84 based)

My solution: I modified Arif-Ali's "02cache" script to accomplish that.
[HD2 Android NAND Development] bhilgeman:
Awesome I'll do that thanks!
[HD2 Android NAND Development] ironheart:
* make a folder, put recovery.img, zImage, initrd.gz and fastboot (from android-sdk) into it. Make sure that you've got a cLK-compatible kernel = zImage!

* open a CMD-window (comand promt) and enter the following:

fastboot flash recovery recovery.img

fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz

This should do it. Afterwards you can boot into recovery by holding the "home" key.
[HD2 Android NAND Development] karendar:
didn't do anything special, but just follow what seadersn says. Install ROM manager, select Desire HD, flash clockwork, when it says completed, go in fastboot and flash CWM back to recovery...
[HD2 Android NAND Development] arif-ali:
that would be great, if you could. :)
[HD2 Android NAND Development] seadersn:
yep, ok, let's say tomorrow am ~ 11:00 @ gmt+1.
[HD2 Android NAND Development] cedesmith:
1.3.3 with full off charge support

just uploaded recovery on post#4 and cwm patch v2 to post#2 with full implementation of off charging.

- amber led will blink is discharging (overheat)

- amber led on if charging

- green led on when full

- power off when charger disconnected

- button backlight will not turn on on keys press

- power the phone with ..... (take a wild guess) ..... power key

lots of thanks to dan1j3l for sharing his code witch was a great inspiration.
[HD2 Android NAND Development] seadersn:
cLK code itself didn't change?
[HD2 Android NAND Development] seadersn:
k, cwm 3.0.1.9, fully patched for cLK, is on the way :)

btw: what does it mean, if LED is blinking green and amber in turn if charging? green - amber - green - amber...
[HD2 Android NAND Development] drewestate:
Pongster, love the new CM7 1.02 build, needed the tethering support with ppp for clk! Thanks.

Thought I would share....

Update zip for those who are using clk, I edited the initrd for ppp data.

This is Hyperkernel V6 with newest initrd from Hyperdroid CM7 1.0.2 and modules. Just flash in CWR

http://xdaforums.com/attachment.php?attachmentid=544963&d=1300389612
[HD2 Android NAND Development] seadersn:
yes/no recovery updated; http://xdaforums.com/showpost.php?p=11935478&postcount=355

have fun! :D
[HD2 Android NAND Development] karendar:
Confused... Do I need to update cLK at all? Or just recovery? :P

Neeeevermind. Answered myself. ;) haha.

This just keeps getting better and better...
[HD2 Android NAND Development] cedesmith:
overcharge blink is on-off every 2 seconds so:

- if blink is 2 seconds then is full-overcharge

- if blink is half second then is full-charge

best way to verify this is connect to usb while off then adb shell and cat /sys/class/power_supply/battery/status to see status

Just recovery... there is a small change to clk too but is peaty small, so small that i did not republish source

In some rare cases (did not figure out why) spl sets boot reason 4 instead of 1 or 6 making cLK not read android boot reason. the change is from if(boot_reason==1 || boot_reason==6) to if(boot_reason!=2) in init.c get_boot_reason()

the only change is
[HD2 Android NAND Development] bhilgeman:
Thank you so much for this recovery. Just flashed it. Thank you for taking all of the "No"'s out is a blessing. It was great when we used phones with a trackball but mashing the volume rocker switch through 6 no's was a pain.

Haven't flashed anything with it yet to test its usefuleness, but it looks good :)
[HD2 Android NAND Development] kaiserlein:
Did anyone try to use MarkinuX HD Extra Clean with CLK? http://xdaforums.com/showthread.php?t=912427

I really love this rom and don't want to switch to another one. He's using last 24MB in Nand for the cache partition.

Any chance to get this working?
[HD2 Android NAND Development] randasecret:
cLK v1.3.2

CWM 3.0.1.9

TyphoonN 2.6.3 CM7

everything is perfect

Can i still use "typhoon kernel(tytung_r7) and initrd for clk " for TyphoonN 2.7.1 CM7

thank you
[HD2 Android NAND Development] karendar:
I don't think the last 24MB is being handled by cLK according to the change log... It's a very nice concept though! Love the idea!
[HD2 Android NAND Development] seadersn:
ok, i will have a look at it, thanks, cede :)
[HD2 Android NAND Development] karendar:
Cedesmith, I'd change this question in your FAQ if you have two minutes:

Q: Should i install it ?

A: If you had to ask probably not. If has no functional benefits over magldr.

Should be:

Q: What functional benefits are there to install this over magldr?

A: Offline charging, ROM manager, fastboot and reboot to recovery, otherwise it has no functional benefits over magldr

;) Seriously, cLK has alot of plus value!
[HD2 Android NAND Development] ironheart:
+1

I second that! By NOW (with full fastboot & RomManager functionality possible via cLK) our beloved HD2 is an Android phone and not a "hacked" WinMob phone anymore.
[HD2 Android NAND Development] ironheart:
@Arif-Ali:

I have an issue concerning your script to mount the cache. The permissions set to "cache" or "cache/recovery" respectively stops market-downloading (market uses the cache mountpoint).

If I don't set the permissions then market is functional but reboot/backup to CWM coming from RomManager stops working (--> simple reboot).

I don't think that my cache partition is too small (20MByte)

What kind of permissions should i set to "cache" and/or "cache/recovery"?
[HD2 Android NAND Development] Satyan:
Anyone ... may be cedesmith can help me with this ?
[HD2 Android NAND Development] arif-ali:
try

chmod 0:0 /cache

instead of

chmod 1000:2001 /cache
[HD2 Android NAND Development] arif-ali:
satyan,

how are you connecting the phone to the PC. I was having similar problems, but not the same problem. I was connecting the phone through USB cable which was connected to a USB hub, and then to the PC, and that was causing problems. If you connect directly to PC, it should work.

If it is not that, then I have no idea
[HD2 Android NAND Development] af974:
Little advice please:

I am patching the kernel with the 3 included in clk source/patch.

Kernel_clk_power_collapse and kernel_off_mode_charging_panel_init_crash were already patched so i did apply only kernel_reboot_reason and it was patched fine but i cannot restart to recovery, i need to add something other?

i used patch -p1 <
[HD2 Android NAND Development] JDM Civic EG8:
If upgrading to the new version of cLK recovery I won't be able to restore my current rom correct?
[HD2 Android NAND Development] seadersn:
for me it worked from 3.0.1.4 to 3.0.1.9 :) backupped in 3.0.1.4 and restored in 3.0.1.9 = rom was booting normal.
[HD2 Android NAND Development] JDM Civic EG8:
Sweet thanks alot for the fast reply! I just finally set up the rom im using perfectly and wouldn't want to do it all over again haha. Last question if doing a restore do i just hit restore? or would I have to do advance restore?
[HD2 Android NAND Development] 2000impreza:
Check /arch/arm/mach-msm/pm.c if the reboot reason patch applied. I've read some people having to apply this patch manually. Never had problems myself using -p1 to apply the patch.
[HD2 Android NAND Development] bhilgeman:
I heard somewhere that you can do a restore but sometimes (not sure when) it doesn't restore the data partition, so after you do "restore" you can do an advanced restore and restore just the data partition from the same backup.
[HD2 Android NAND Development] seadersn:
@ jdm: simple restore :)

@ bhilgeman: this happens only if you're not formatting data/cache/.secure with "wipe data / factory reset" first. if you don't do this, the partitions are in vfat format, which isn't the correct one; as i understood :D
[HD2 Android NAND Development] af974:
Thanks impreza,

in fact i did see previous post by pongster and this problem so i did check if the patch was apply and it is but the strange thing is that i have some lines that i didnt have in original pm.c :

#if defined(CONFIG_MACH_HTCLEO)
// if cLK is bootloader 0x0 is protected and not writtable but cLK changed reset vecotr to jump at address stored at 0x11800004
if(htcleo_is_nand_boot()==2){
pr_info("msm_pm: 0x00000000: %x\n", msm_pm_reset_vector[0]);
pr_info("msm_pm: 0x00000004: %x\n", msm_pm_reset_vector[1]);
msm_pm_reset_vector = ioremap(0x11800000, PAGE_SIZE);
}
#endif

should i delete them?

EDIT: nevermind, it seems that kernel was not patched with clk 1.3.1 patches, thanks anyway i will reassembly kernel.
[HD2 Android NAND Development] seadersn:
some people asked for this, so here they are:

1mb misc

3mb cache

5mb boot

5mb recovery

100 to 400 mb system

@ each: rest = userdata.

find it attached. inside the archive is the "flashaholicsRUU.exe", it performs a task29 first and then will flash the RUU_signed.nbh. for flashing one of these layouts, rename it by removing the number, which tells you the system partition size. there should be one applicable for everyone.