yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Blubster:
Weird, rom manager is supposed to put files inside this folder for CMR. If i understood it correclty...

Maybe the permissions of the folder are not right...

I would suggest a rather extreme solution (backup if you want), which is to delete completely the cache folder in /data, IF you can use a computer with adb as it has to be done in recovery mode, with /data mounted...

The cache folder should get created, if not present, during your rom's boot.

The step by step are :

- reboot your phone in recovery mode

- go to advanced, in clockwork menu, and select mount data

- plug in your phone to your computer and do adb shell

- type : cd /data

- then : rm -r cache

- unmount /data

- select on clockwork main menu "clear /cache" (which will clear /cache partition not folder)

- reboot!

hopefully the cache folder should get created again, and should work, given the 02cache script you have in /etc/init.d is correct.
[HD2 Android NAND Development] Stephen:
I have noticed that when rom manager reboots the phone, I go in and check the mounts and I noticed that the /cache folder is mounted, but the /data folder is not. Does this make a difference?
[HD2 Android NAND Development] seadersn:
that's normal; partitions (system, data, boot) aren't mounted in cwm normally / automatically @ start of cwm.
[HD2 Android NAND Development] tytung:
I think my cLK_ppp_tytung_r9_update.zip have inappropriate settings for ROM Manager.

Please flash cLK_ppp_tytung_r9_update_v2.zip.

V2 includes Cedesmith's libhtc_ril_wrapper.so v8.0b3 and fixes Backup Current ROM feature in ROM Manager.
[HD2 Android NAND Development] Stephen:
Confirmed it is now working. Thank you for all your help guys, I now have an awsome phone running gingerbread that I can backup and also charge whilst switched off! Cheers all!
[HD2 Android NAND Development] djbarney:
Hiya Arif, thanks for the help, i've been too busy to check the forums here since i posted, but i just wanted to follow up on the issue i posted here: Tytung has issued a fix for this specific problem here!

With this update installed, rom manager now works correctly: when selecting backup, it'll ask nicely for the backupname, reboot into recovery and start the actual backup, brilliant! Thanks a lot for the help offered so far m8 :)
[HD2 Android NAND Development] songokussm:
i skimed the last 8 pages and did not find this reported.

3.0.2.5 has a turning on bug.

when you press power, and the phone is plugged in, the button lights turn on and stay on, but the phone does not do anything.

however when the phone is not plugged it, it works fine.

3.0.2.4 did not have this issue.

charging works just fine.
[HD2 Android NAND Development] seadersn:
yep, known: this is due to using koush's "offmode charging for htc devices" method, which is incl. @ source already :) maybe he will fix this some time; but it isn't necessary. in version .4 cedes patch was used.
[HD2 Android NAND Development] arif-ali:
Yes, we know about that issue. A minor one, but yes. This is code within the cwm that needs to be fixed. We'll report it, and try to get it fixed.

The previous one had code from cede, as the facility of off mode charging was there in cwm, but not enabled for leo. We got that enabled in 3.0.2.5. We will try to get this fixed in the next release
[HD2 Android NAND Development] seadersn:
and who knows if this really is an issue or just the usual way for every htc phone with cwm installed :) we were fastidious with cedesmith's solution for that thingy.
[HD2 Android NAND Development] q9650:
Does this work with rafdroids 4.0.2? Or does it not matter what ROM i use?
[HD2 Android NAND Development] arif-ali:
A CWM is a ROM independent, the whole point of it is, use it to install/backup/restore ROMs
[HD2 Android NAND Development] mattfmartin:
I was wondering why development is currently "paused"?
[HD2 Android NAND Development] arif-ali:
He's on holiday probably with limited access. Plus it can only be updated when new recoveries come through on the git repositories anyway; plus if there is something new, I can support in the interim, and if seadersn agrees, will get the cLK and magldr versions in the threads here with the yes/no patch.

Plus, We don't develop the recoveries, we just bring it to the HD2's with HD2 quirks.

Were you looking for something special to be added :)
[HD2 Android NAND Development] anouarhozman:
In my country the ppp mode don't fonction good with the new clk their is some rmnet mode????

Sorry for my bad english
[HD2 Android NAND Development] arif-ali:
There is no rmnet for cLK.

have you tried the new libhtc_ril_wrapper from cedesmith

original file:

http://xdaforums.com/showpost.php?p=13040435&postcount=1172

CWM update file:

http://xdaforums.com/showpost.php?p=13042798&postcount=1174

if the above option doesn't work, then magldr is your only option.
[HD2 Android NAND Development] zach.antre:
cwm that allow cLK ROMs to run on MAGLDR

http://xdaforums.com/showpost.php?p=13117123&postcount=1272
[HD2 Android NAND Development] anouarhozman:
Thank you i will try this.
[HD2 Android NAND Development] mattfmartin:
No I'm good;p Was just wondering what was going on.
[HD2 Android NAND Development] slammly:
when doing a clean install on the hd2, do i have to install the older recovery img and then update to this one? or can i straight up just replace the raw recovery img with this new on install?
[HD2 Android NAND Development] seadersn:
you can install it straight without flashing a prior version ;)

'paused' only means, that i have limited time for the next two months for providing this special yes/no version :)
[HD2 Android NAND Development] barty22:
Can I flash the most recent CWM (3.0.2.5) over an older CWM installation that is on my phone (3.0.1.4), while keeping my CLK installation and my Android installation completely intact and without any issues? Or is it recommended to do a clean install when updating CWM (task29, radio, clk, cwm, rom)?

Thx in advance :)
[HD2 Android NAND Development] D4rk50ul:
I do it all the time in fastboot.

Sent from my HyperDroid powered HD2.
[HD2 Android NAND Development] tageeboy:
Rom manager now supports hd2 and makes flashing soo easy. Give it a try sand you will be hooked.

Sent from tin can with string.
[HD2 Android NAND Development] arif-ali:
CWM 3.0.2.7

Hey guys,

Here's an updated CWM 3.0.2.7, with yes/no patch

3.0.2.7 on RM should come soon. It's up for review at the moment

enjoy!!!
[HD2 Android NAND Development] Kameirus:
I can just flash this thru cwm without having to do a complete reinstall correct
[HD2 Android NAND Development] arif-ali:
no, these are not CWM flashable images, will do them in a bit
[HD2 Android NAND Development] Kameirus:
Ok thanks or should I just wait for the RM version since I'm gonna start trying. To use it
[HD2 Android NAND Development] arif-ali:
OK, CWR images added to the previous post

see the link below with the new attachements

http://xdaforums.com/showpost.php?p=13175309&postcount=417
[HD2 Android NAND Development] Kameirus:
Thanks
[HD2 Android NAND Development] seadersn:
thx arif :)
[HD2 Android NAND Development] arif-ali:
updated again, magldr issues.

late night :(
[HD2 Android NAND Development] `SBR`:
fyi..

Magldr img is not working. both CWM and DAF flash way..
[HD2 Android NAND Development] D.O.C:
Arif, do they support reiserfs as previous versions?
[HD2 Android NAND Development] clyder:
I get stuck at gogogo after installing 3.0.2.7 for magldr. Reverted back to 3.0.2.5.
[HD2 Android NAND Development] scariola:
CLK 3.0.2.7 flashed fine!!
[HD2 Android NAND Development] arif-ali:
for those using MAGLDR, sorry guys, the code got changed for where the baseboard is, so doesn't work, been trying to fix this morning. Will have an updated one later.

I went to MAGLDR specifically to test this (first time in 2 months), so this is now fixed in my code.

looks like the version will be updated to 3.0.2.8.
[HD2 Android NAND Development] arif-ali:
yes, nilfs, btrfs, and reiserfs
[HD2 Android NAND Development] arif-ali:
CWR 3.0.2.8

OK, here is the update as promised

I have tested the both magldr and clk builds myself, so should work.

Any problems, let me know
[HD2 Android NAND Development] nic.stl:
downloaded and installed MAGLDR version .... in test now

thank you arif-ali :)
[HD2 Android NAND Development] nic.stl:
Everything seems to work properly.

Good job !
[HD2 Android NAND Development] Traukoman:
Hey Arif, thank you for your work, but and i have to tell you i can't download this file, others are ok for download

recovery_leo_magldr.img.zip (4.72 MB)

Maybe you could check and reup.

Thanks!
[HD2 Android NAND Development] arif-ali:
I have just tried downloading, and it works for me (13 others have downloaded, if the stats are right against the download)
[HD2 Android NAND Development] dude0316:
Works perfect !
[HD2 Android NAND Development] seadersn:
jep, nice one; thy again for keeping us updated ;)
[HD2 Android NAND Development] clyder:
Just installed magldr 3.0.2.8. Works great.
[HD2 Android NAND Development] Lozone:
3028 works perfectly.

Thanks.
[HD2 Android NAND Development] Nikola G.:
Thank you arif. I did not know you could flash CWR via CWR :) Change log for 3.0.2.8?
[HD2 Android NAND Development] seadersn:
first post...

a changelog as we know it isn't available :(
[HD2 Android NAND Development] arif-ali:
The changelog as usual that there is a link to github for that, but here's a brief changelog between the last one and this one

remove old chargemode crap

fix bug where the wrong SD Card block gets partitioned. rely on the ftsab to glean the sdcard mmcblk

bml fixes

format .android_secure on RM data wipe.
[HD2 Android NAND Development] despy1989:
Upgrade CWR on CWR. awesome...... worked flawlessly......thanks team........
[HD2 Android NAND Development] clyder:
I posted the magldr 3.0.2.8 flash files to a Ultimate Droid thread with config file for that build.

Some people, so far everyone with 3.0.2.4. tried to flash it via terminal emulator with flash_image command and got an error so they had to do it through DAF.

I, on the other hand updated to 3.0.2.8. from 3.0.2.5. without any issue with flash_image command in terminal.

Is this some known issue (sorry if there is an answer to this, couldn't find any)?

Just wanted to point it out in case that is an updating from 3.0.2.4. or lower issue.

In that case....do your backups before trying...
[HD2 Android NAND Development] arif-ali:
ok, could be that the size of the recovery img file is too big for the partition, and could not fit in the current partition. By default, the size of the recovery image is what is the size of the partition, so even the slightest increase in size of the image, it will not flash.

Some on the other hand keep it static at 5M, and then there is a bit of maneuverability with the size of the image.
[HD2 Android NAND Development] seadersn:
from 3.0.2.4 to 3.0.2.8 the filesize increased about 1mb; if the cwm version which was present before update was flashed with dft android flasher and the 'filesize' tag (and not a fixed partition size like 5mb) in flash.cfg, then the errors are normal, just because of partition size of recovery partition in magldr roms, which was ~ 3,2mb with 3.0.0.5/6 versions up to 3.0.1.9.

yeah, arif was faster :D
[HD2 Android NAND Development] l0rdsheva:
last time rom manager tell me that there was the 3.0.2.5 update. Why this time it say there's no update even if 3.0.2.8 is out?
[HD2 Android NAND Development] arif-ali:
That;s because it is not there at the moment, it is currently in the process, We will let you know when it will happen

It's a long process this time, as I had a new kernel, and had to get the code changes in to git.
[HD2 Android NAND Development] l0rdsheva:
ok, no problem at all, just flashed the cwm one and i'm happy with my new toy :D
[HD2 Android NAND Development] clyder:
Yeah, config file is with filesize tag. And my last CWM that was flashed with USB Flasher was 3.0.2.5. Versions 3.0.2.7-8 I flashed via terminal. I was the lucky one I guess. :)

Thanx
[HD2 Android NAND Development] slammly:
hi.. newb question.. so i replace the img file from 3208 into the 150m recovery file and rename it to recovery-raw.img.... then what should i do with the meta-inf folder provided with the magldr version?

edit: nevermind, I put zip on sd and installed it from 3025. sorry and thanks
[HD2 Android NAND Development] :
New recovery version 3.1.0.0 is available in Rom Manager.

..unfortunatly it throws an error for me when i try to update =/
[HD2 Android NAND Development] arif-ali:
I will have a look today, on why there is a problem

Edit: The variables have been added to the file, but the image has not been created yet. Will get this solved soon
[HD2 Android NAND Development] tropicanapure:
I noticed that too. But I rolled back the install when it failed (probably) because I was short of space on recovery. :(

So out of curiosity, anyone know where can I see the CL for v3.1.x?
[HD2 Android NAND Development] arif-ali:
The one we compiled, is based on the latest source code, so if they have changed is internally to 3.1.X, then I am not sure about that. If there is a new version, We'll get it compiled here with the yes/no patch

There are changes since we have compiled 3.0.2.8. But not significant as yet. The version number in the code is still 3.0.2.8
[HD2 Android NAND Development] djbarney:
seems like the problem with the 3.1.0.0 version has been fixed, i've just flashed the new [3.May][cLK/MAGLDR] NexusHD2-Gingerbread V2.7 [GRJ22/Android2.3.4][Kernel:tytung_r10] rom, tried updating my clockworkmod version with rom manager and it said it succeeded. Rebooting into recovery confirms v3.1.0.0 running now. Didn't spot anything new or changed, but it's good to know they're working on it ;) so i guess it should now work for you guys as well
[HD2 Android NAND Development] kaiserlein:
Confirmed, worked for me too
[HD2 Android NAND Development] bobmarsh72:
+1 on gbx v12

Tried about an hour ago, didn't work. Saw your post and tried again, and worked 1st time.
[HD2 Android NAND Development] arif-ali:
Good stuff,

The new version should also have the same kernel as the one I built earlier, so nilfs, reiserfs, btrfs support
[HD2 Android NAND Development] DAP420:
When I did I I got an error saying image was not there. I did exactly the way you guys did it then I booted into magldr then hit ad recovery. What happened
[HD2 Android NAND Development] arif-ali:
The recovery in RM isn't supported with magldr at the moment. We (me and seadersn) are testing and hoping to get something working such that the same recovery works with both cLK and MAGLDR, so that we can get rid of all the confusion.

Give us time, and we should have something ;)
[HD2 Android NAND Development] seadersn:
yay, and this isn't looking promising for me :( the tests weren't successful; to get this running on both m+c "some modifications" of source code are necessary, from my knowledge. i don't know enough of this coding stuff to do this, and in my opinion the code of cwm source should stay clean, too. it's on koush, i believe :) maybe it's possible to find a solution which isn't "too expensive".
[HD2 Android NAND Development] arif-ali:
Hey,

I have also been looking into this, and the best way or us to achieve this is by using the postrecoveryboot.sh script, which somehow detects the booloaders, and changed the recovery.fstab on the fly. Off hand there is no way to do this unless the bootloaders themselves add something to the system properties, or /proc/cmdline.

cedesmith has said that in the next version of the cLK, he will add clk=1.4.1 onto the cmdline, so we could easily catch this. So if we go with the script method, then everyone on cLK will need to move to the modified version. I was going to test this myself by changing the cLK code, but haven't had the opportunity to test yet. maybe will have a go sometime this week.

So in essence we could do the following, (once the code changes are in)

if [[ ! `grep clk= /proc/cmdline` ]] ; then
sed -i 's/\/boot\t\tmtd/\/boot\t\tyaffs2/g' /etc/recovery.fstab
fi
[HD2 Android NAND Development] Yom:
Got 3.1.0.0 from RM, how to enable two-line YES/NO confirmation?

Hi all,

Just installed the latest from RM on my HD2, and noticed that the 2-line YES/NO confirmation is back to the 10 NO NO NO NO YES NO confirmation... any tips on how to return it to the simpler 2-liner?

Thanks!
[HD2 Android NAND Development] seadersn:
yep, flashing the version offered here at this thread :-) the version @ RM is the official one, unedited.
[HD2 Android NAND Development] Yom:
thank you sir! Any ETA for the enhanced build? I can't find it in the thread...

Posted using my hacked, rooted, undervolted, overclocked, pimped-out and overall bad-ass Samsung Galaxy Tab.
[HD2 Android NAND Development] arif-ali:
There is no 3.1.0.0 in the sources yet

It is still 3.0.2.8, which I have provided in one of the previous posts. I don't decide which version goes out in RM, koush pushes it out an does the numbering himself. So it could be that the real version is 3.1.0.0, but the source code has not been updated.

So it is 3.0.2.8 until further notice
[HD2 Android NAND Development] arif-ali:
OK,

after some testing, I think I may have it working such that the same recovery works for clk and magldr

Below are the links

cLK 1.4.arif Beta with my changes for cmdline

recovery_3.0.2.8-leo-beta.img

if people with magldr, can test the recovery above, and cLK guys who use 150M, and 5M cache use the above cLK to beta test for me, then that would be great.

It would be really useful for you guys to report yes or no, or whre people are facing problems

PLEASE be aware, this is a test release for TESTING, so not for production, please, if the tests are successful, then we will release new cLK and recovery for main use.
[HD2 Android NAND Development] seadersn:
:) sounds nice; will test it when i'm home again! should be tomorrow evening; i hope... depends on girlfriend ;)
[HD2 Android NAND Development] zach.antre:
cLK link doens't work

CWM doesn't work on normal clk 1.4 135/2
[HD2 Android NAND Development] arif-ali:
yes, I know, that is why I have the modified clk. this CWR will work correctly with the modifications that I have made in cLK.

I will create layouts for this modified cLK if people want

Edit: my bad, the link doesn't work, will be up in a few minutes

Edit: Link in previous post updated, apologies for the wrong link

Anyone interested in looking at the changes made

https://github.com/arif-ali/android_device_htc_leo

https://github.com/arif-ali/cLK

Edit: layouts for people

cLK_1.4_layouts_arif_test.zip
[HD2 Android NAND Development] zach.antre:
Will test tomorrow, going to sleep now... Arif, I posted an idea on clk thread, would it be easy to make clk to search for /SDcard/recovery.img and flash it by pushing a button? That way there is no need for pc anymore.
[HD2 Android NAND Development] clyder:
I am on magldr. Just tried flashing this via terminal emulator 'flash_image' command and I got many errors like:

mtd:read error at 0xsomething (Out of memory) followed by some no space on device error and lots of read write errors. I flashed old 3.0.2.8. back the same way.

I have filesize tag in flash.cfg, I know that you explained to me that it could cause errors, but I havent had any problems in old 3.0.2.8. Do you recommend keeping it fixed size?

Anyway, I will also try to flash it via DAF later.
[HD2 Android NAND Development] arif-ali:
Yes, it would be the same reason. Personally if I was on magldr, then I would use fixed size. We compile against the assumption of max size of recovery to be at 5M. So if you kept it at 5M, I don't foresee any further issues
[HD2 Android NAND Development] clyder:
Thanx for the tip. What I did now was:

- CWM backup

- flashed 3.0.2.8. via DAF and with 5M instead of filesize

- entered recovery without problems (now it says clk ClockworkMod Recovery 3.0.2.8...)

- it is restoring now, so I guess that it works

I need to go now, but I will report if there is anything wrong with beta.
[HD2 Android NAND Development] clyder:
And it booted fine, so restore was done without problem.
[HD2 Android NAND Development] arif-ali:
It says clk because, that was the base. It would be useful to do

adb shell cat /etc/recovery.fstab

To see everything has changed
[HD2 Android NAND Development] clyder:
Yeah, I guessed that. Sorry if it sounded like a complain. I will try adb when I get home.
[HD2 Android NAND Development] clyder:
Just tried this but got '/etc/recovery.fstab: No such file or directory'...

I also looked in phone and there is no recovery.fstab file anywhere.
[HD2 Android NAND Development] arif-ali:
Sorry, should have made it clear. Run the command when you are in recovery
[HD2 Android NAND Development] clyder:
# mount point fstype device [device2]

/boot yaffs2 boot

/cache yaffs2 cache

/data yaffs2 userdata

/misc mtd misc

/recovery mtd recovery

/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0

/system yaffs2 system

/sd-ext auto /dev/block/mmcblk0p2 /dev/block/mmcblk0

I hope this helps...
[HD2 Android NAND Development] arif-ali:
Cool, that is the expected result. More testing from others would be appreciated. clk and magldr
[HD2 Android NAND Development] zach.antre:
Here are my results on modified cLK 1.4

# mount point fstype device [device2]

/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/sd-ext auto /dev/block/mmcblk0p2 /dev/block/mmcblk0

Everything is working fine so far...
[HD2 Android NAND Development] arif-ali:
So, again that is the expected result. The thing to look out for is the fstype of boot; for magldr it needs to be yaffs2, whereas for clk it needs to be mtd.

Happy testing ;)
[HD2 Android NAND Development] zach.antre:
And these are the result on MAGLDR with rboot

# mount point fstype device [device2]

/boot yaffs2 boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/sd-ext auto /dev/block/mmcblk0p2 /dev/block/mmcblk0

So same CWM recovery works with both... cLK and MAGLDR :)

Next step is RM working on MAGLDR?
[HD2 Android NAND Development] arif-ali:
This can only work when magldr has the boot reason facility, in the same way cedesmith did that for cLK, until that feature is implemented by the DFT team, RM with magldr will not work. (maybe someone can nudge them if anyone has any influence on the DFT guys)

once we have tested and made sure that this CWR works, then the MAGLDR guys will also be able to flash recovery from RM. So this is one thing that will work with RM.
[HD2 Android NAND Development] zach.antre:
nice... then it just need to be official! cLK v1.4.1 and CWM 3.0.2.8 v2
[HD2 Android NAND Development] arif-ali:
well, afaik, cedesmith is working on cLK 1.4.1 and similar modifications will be made by him and probably others (I don't know what he is planning) . The modifications by me are only interim (a hack), and not perfect, and only for testing purpose; and they were only made for the purpose to test the functionality of CWR to be compatible with both cLK and magldr. I would probably need to spend a bit more time, to fix it up so that it is a bit better. If I do release it, it will not be 1.4.1, maybe 1.4.0.1.

If I also release the new CWR, it will no doubt not work with the current cLK, so I will delay until I am sure it is working. I have got 2 people confirmed and I am 3rd, I think for me, that is not sufficient enough for me to say yes, this definitely works. You might use it differently to me, and another, so I would like people to test for a week, before I will say that we release it.

i hope that makes sense.
[HD2 Android NAND Development] arif-ali:
OK, after some testing, I have the following cLK, which I think is working well. This is my version on top 1.4 from cedesmith. So my version is 1.4.0.1

My changelogs can be found here

https://github.com/arif-ali/cLK/commits/master

download from the files attached

Note: for cLK users to use the CWR's below, you need to use the new cLK attached, otherwise the CWR will not work.

regards,

Arif