yashsingh1/xdaforums huggingface dataset:
[Fascinate General] badogg:
My wife just got a fascinate, I haven't root'd it or anything. Yet. ;)

The battery life is horrible compared to my Dinc, even when my Dinc was running stock unrooted Froyo. I was hoping that the Froyo update that the fascinate just downloaded and installed would have helped with it, but it actually seems to be a little worse.

edit: Do I even have any options being it is not root'd? I'm betting it is because the wifi is on all day and not connected to wifi at work. She's not savvy on all that stuff, so I'm going to have to teach her.
[HD2 Android NAND Development] arif-ali:
Hi, folks

ClockworkMod Recovery (<- source).

"Changelog of ClockworkMod Recovery"

changes are here for some of the work we have done for support in RM

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

https://github.com/CyanogenMod/android_device_htc_leo

changes for the yes/no patch, and anything provided in this thread are here

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

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

If you cannot wait for new builds, then Arifs nightly builds are available here.

Features:

Based on 5.0.2.6 sources

Re-coded recovery and leo gits in few places to have the same CWR working for both MAGLDR and cLK

Fixed cLK with versioning in cLK to add clk=1.4.0.1 to /proc/cmdline

Now require cLK 1.4.0.1, rather than the 1.4 from cedesmith

Compiled using official Offmode-Charging Fix by Koush

Edited confirmation menu to show one "no" only

Re-arranged YES / NO: YES now is on first place

ReiserFS and NILFS Support

Offmode-Charging with cLK ONLY

SD-EXT backup / restore (no matter if Reiser, NILFS, ext 2/3/4)

You can flash this image easily from within Android; simply copy the file onto your sdcard and run following commands:

$ su
# flash_image recovery /sdcard/name_of_recovery_file.img

Maybe the flash_image command is not available on your build; you can find it attached. Copy it into /system/bin folder and run following in terminal emulator:

$ su
# chmod 777 /system/bin/flash_image
[HD2 Android NAND Development] seadersn:
August 7, 2011

Newest sources 4.0.1.4

June 10, 2011

4.0.0.0 sources

Changelog of recovery:

- added the efs partition to the do not format list

- also fix up the /sdcard symlink on startup

- tar nandroid and /data/media support

June 8, 2011

3.2.0.1 sources

Changelog of recovery:

- Rename format_ignore_partitions to a forbid_format

- Fix 6 extentedcommands declaration warnings

June 3, 2011

3.2.0.0 sources

Added changes necessary for compiling "one recovery for all"

ClockworkmodRecovery now works for MAGLDR and cLK, no extra recovery for each loader

Added new cLK 1.4.0.1 partition layouts as attachment

Arif is continuing this for unknown time: thank you very much, Arif :)

April 18, 2011

3.0.2.4 sources; renamed to 3.0.2.5

Compiled with Koush's Offmode Charging fix

Attention: Filesize is ~ 1MB bigger than previous version due to new Offmode Charge Fix (i believe); it still fits into 5MB Recovery Partition Size

SD Version is only working if power or USB is plugged in -.- Working 3.0.2.4 Version here

April 13, 2011

Updated to newer 3.0.2.4 sources; see "changelog" link in first post ;)

Full support for REISERFS & NILFS filesystems

cLK and MAGLDR will follow

Added zip file containing cedesmith's offmodecharging and my edits as "patch" (diff) file

Added another flash-method and attached the binary which is necessary

March 29, 2011

Added some cLK_1.4_partition layouts; attached on this post

Normal Cache-size Version (usable for most cases):

boot 5M

cache 44MB

recovery 5MB

misc 1MB

system 80-160MB in 10MB steps, 180-400 in 20MB steps

userdata = rest of available NAND

Small Cache-size Version (requires initrd.gz which links /cache to userdata partition):

boot 5M

cache 5MB

recovery 5MB

misc 1MB

system 80-160MB in 10MB steps, 180-400 in 20MB steps

userdata = rest of available NAND

stirkac made an exe installer with these layouts; it installs cLK and the desired layout automatically. You can find it here. Thank him :)

March 25, 2011

Updated to 3.0.2.4 sources

March 17, 2011

Updated to 3.0.1.9 sources

cLK was updated to latest patches from cedesmith incl. complete offmode charging support (LED color changing, button press behaviour etc)

March 15, 2011

Backup'n Restore does what it is intended to

cLK is running well and was updated to latest patches from cedesmith

MAGLDR is running well if restored backups are from same version

March 14, 2011

Second run, needs testing by MAGLDR users regarding full restore (mainly: Boot partition!)

cLK is running well

March 10, 2011

Initial release, 3.0.1.4, English only

Bug with MAGLDR; removed

Notes:

- Backups from a previous version can't be restored with this one. However, backups from this version are fully working.

- Offmode charging is only possible with cLK; MAGLDR up to 1.13 isn't capable about that at this time, maybe in future releases.

- MAGLDR Versions are untested by me, here i'll need your feedback, especially regarding restorings from earlier versions (e.g 3.0.1.4 backup restored in 3.0.1.9 = working or not).

CWM "ChangeLog", but w/o Version No.
[HD2 Android NAND Development] dharvey4651:
Awesome. Only thing we really need now is a change log between different CWM versions as they come out.

PS>> Gave you an extra post in case you need it later.
[HD2 Android NAND Development] seadersn:
hmm, i'll look around if an official changelog already exists, otherwise i have to figure this out and write for myself, yes.

and thx for extra post :D
[HD2 Android NAND Development] karendar:
Hard to find an actual version history... All I found was ROM Manager's version history:

http://gh-pages.clockworkmod.com/ROMManagerManifest/CHANGELOG.txt
[HD2 Android NAND Development] WarlockW:
Nice Work ..

Cool.. Will Save On The Poor Vol Down Key!

Nice Work ..
[HD2 Android NAND Development] shakeym:
Cool nice job well done...
[HD2 Android NAND Development] elmmis:
wooow~try it right now ! thank you!!
[HD2 Android NAND Development] seadersn:
@ karendar: thx for looking too. but it seems, there isn't one available, not even in the sources... maybe @ forum, but haven't found sth until now.
[HD2 Android NAND Development] -Spyros-:
EDIT

It works! : D

No more "No's": D

And the function "PowerOff" is rly nice :P

@seadersn,

kommt das auch auf Handy-FAQ? :P

Thnx

Greetings.
[HD2 Android NAND Development] seadersn:
xD hab ich's mir doch gedacht ;) jap, wird's :-) voraussichtlich in den nächsten drei stunden.

jep, it will :-)
[HD2 Android NAND Development] -Spyros-:
Freu mich schon :D

Könntest du die ganze Recovery übersetzen [E-D]?

Oder ist das unmöglich?

Could you translate the whole recovery?

Or is that impossible?
[HD2 Android NAND Development] seadersn:
nope, this isn't impossible; but this is really too much for me atm ;) maybe in about a week, german only.
[HD2 Android NAND Development] -Spyros-:
We can wait ;)

You have so much time:P

Thnx.

Greetings.
[HD2 Android NAND Development] Life Engineer:
BEAUTIFUL!

Can this be used with MAGLDR 1.11!?!?

If yes can you please provide me with the kernel and initrd to replace the existing ones on SDcard!?

Thx
[HD2 Android NAND Development] pongster:
Any chance you can add reiserfs and btrfs support when making a Nandroid Backup and Restore? :)
[HD2 Android NAND Development] karendar:
https://github.com/CyanogenMod/android_bootable_recovery#

Here's the original Github for the Gingerbread Clockwork recovery... I haven't programmed in so long I don't think I'm of any help with this.

Pongster, I'm digging through gits to see if anyone had this implemented already in a modded version.
[HD2 Android NAND Development] seadersn:
hi,

thx for the github link; anyway i've already added it to the first post :) unfortunately a changelog or sth similar isn't arising from the sources :( but thx, again.

regarding reiser+btr: i don't know this much of programming, what i did was an (easy) change of existing code, but if it's already present in the source code and one only needs the mount points, this is no problem, i believe :)

i can have a further, deeper look into that, but it would take a while if it's not present and i have to change the code and i will definitively need help. no assurance about that ;)

regarding magldr 1.11: life engineer, i will pm you a version for testing. maybe tomorrow morning, GMT+1?

@ spyros, from where do you know that i have plenty of time, he? :D ;)
[HD2 Android NAND Development] arif-ali:
hey seadersn,

I have been looking at the compilation of recovery as well, and a thought about drivers came about. Which kernel are you using are using the same one in device/htc/leo, or the one compiled by cedesmith. I think in order to get the reiserfs or btrfs, then all we need to do is compile our own kernel with the mods, and put it in the right place and it should work.

I will give it a test with my kernel this evening

with respect to the initrd and zImage, that's easy to get, You need the following 2 files

out/target/product/leo/kernel

out/target/product/leo/ramdisk-recovery.img

but again this needs testing, unless someone else can confirm this
[HD2 Android NAND Development] karendar:
seadersn, check this out: Post from the desire forums... Looks like ReiserFS might be supported in Clockwork directly. Just need to edit .config:

http://xdaforums.com/showpost.php?p=10488102&postcount=432

Alot of the kernels already have ReiserFS and btrfs, I believe...
[HD2 Android NAND Development] arif-ali:
@seadersn, do you want me to post my version for you to check out? To see if you have the same problem.
[HD2 Android NAND Development] pongster:
Quick Question... do we need to reflash cLK before using this new CWM from you?

or are the only changes kernel patches that fully support off charging?
[HD2 Android NAND Development] seadersn:
arif, YES, please :-) would be great!

and pongster, nope, no need for reflashing, only kernel related things, respectively recovery, jep.
[HD2 Android NAND Development] pongster:
Thanks. will try patching now. :)
[HD2 Android NAND Development] af974:
I dont understand this led issue anyway i have this situation:

Device on Clk Menu= no blinkin red light while charging

Device on CWM= No led at all

Device on= no blinkin red light while charging
[HD2 Android NAND Development] arif-ali:
I have attached it to this post now

I am not sure if it will work with MAGLDR, as I don't use it, but I know it works with cLK
[HD2 Android NAND Development] seadersn:
very nice :) thx so far; which kernel did you use for compiling it? i'm testing it.
[HD2 Android NAND Development] arif-ali:
Using my kernel, with all cLK patches
[HD2 Android NAND Development] seadersn:
it works :wall: ok, then i will use another kernel at next try; thank you for posting it ;) and now: sleeping...
[HD2 Android NAND Development] brockyneo:
Hi guys quick question is it safe to flash new version over old and is it save to flash without touching the nand rom many thanks
[HD2 Android NAND Development] seadersn:
yes it is safe, np.
[HD2 Android NAND Development] arif-ali:
Yes, no problem at all

that is what I do anyway

btw,

Here's another way to flash (for those people who have flash_image in their ROMs):

* run "adb push recovery.img /sdcard"

* run "adb shell flash_image recovery /sdcard/recovery.img"

* then reboot into recovery, by reboot and hold the home key.

I have been using this method for the last 2 releases. and works without a problem for me.
[HD2 Android NAND Development] Blubster:
This morning after the charge of the night it was fixed green (if i am not mistaken...), though when i tried again, it was blinking amber/green like you said! Not only green... So it may not be kernel related, i don't know... :S
[HD2 Android NAND Development] seadersn:
updated the recovery with fixed version; LED works now as it should for cLK ;) thx to arif i've found out that the kernel was broken :(
[HD2 Android NAND Development] stab244:
So if I have MAGLDR 1.13 and want to update to the latest CWM, I would have to rid myself of my ROM first because the partition layout would be reset?
[HD2 Android NAND Development] `SBR`:
can we flash cLK recovery using ROM manager or from phone itself..

right now in office can't install ADB toolkit..
[HD2 Android NAND Development] arif-ali:
If you have flash_image available on your phone

then copy recoveryXXX.img to phone (e.g. /sdcard)

then run "flash_image recovery recoveryXXX.img" in a terminal on the phone
[HD2 Android NAND Development] pongster:
Cool. I installed seaders latest cLK CWM and when plugging in the device while in recovery, the LED's don't light up.... is this normal or do I need to be patching my kernel again for this? (patched it the other day for the 1.3.2 :))
[HD2 Android NAND Development] mattfmartin:
This is starting to get way too confusing with all the different layouts floating around.

Sent from my HTC HD2
[HD2 Android NAND Development] silverwind:
+1

I tried to flash recovery using boot AD SD within MAGLDR, and now for certain reason which I don't know, if I flash recovery using USB Flasher within MAGLDR, it never boot (error: cannot read kernel image) [sorry, I also post about this in General thread]
[HD2 Android NAND Development] seadersn:
good morning everybody!

@ layouts: yep, we really need two versions:

- one with small cache for chefs which are linking cache into the data partition and

- one with cache "as usual", sized ~ 44mb

sizing the system partitions adequate for everyone is not really possible, i believe. have a look @ DAF flasher versions, here the system partition in most cases is depending on filesize of the system image, there are much more variations available than for cLK.

@ silverwind: what exactly is your problem? :D recovery doesn't boot, no matter if used via sdcard or nand? maybe i've made a mistake whilst cokmpiling it, please tell me more, as i didn't test the magldr versions due to no more using it. but i thought they should work as usual.
[HD2 Android NAND Development] mattfmartin:
Top of the morning Seadersn. Question about rom manager. In the PRO version, when you can select to check for updates on a build. Is that just fir supported CM devices? Also why won't Cyanogen put our phone in the supported devices section? Our phone is as native as can be, except for getting OTA updates.
[HD2 Android NAND Development] seadersn:
yep, it is. but one can contact koushik dutta and request his rom to be in the update list. the rom chef needs to submit a java script file, which contains the necessary data such as rom name, server to check for downloads etc.

i believe charansinghs version for example will be available for us pro users soon :)
[HD2 Android NAND Development] illuzi0n:
dw will figure it out ..
[HD2 Android NAND Development] seadersn:
wowow... post this in cLK thread, pls; and a question: what happens if installed "the usual way" with "fastboot flash recovery xxxxx.img" ...?

another question: which layout are you using?
[HD2 Android NAND Development] mattfmartin:
Yea I used to use his build, but stopped until he gets finish with his school stuff. Will be really nice when we finally get to see our device in cm forum
[HD2 Android NAND Development] silverwind:
I posted my question in this link: http://xdaforums.com/showthread.php?p=12233670

I can boot into Recovery using AD Boot method. But if I use USB Flasher to flash Raider x Recovery, then I cant boot into Recovery (after flash), it always says ERROR cannot read kernel image

Please check the above link, i hope you can help;)

thanks in advance
[HD2 Android NAND Development] seadersn:
i've installed magldr for testing this out and unfortunately this is working with no problems :( and i have no idea what could cause this at your side; i'll hop over to your thread and have a look at it. we will get this :)
[HD2 Android NAND Development] silverwind:
Maybe, there is damage in my physicall NAND :(

Now, I go back to Winmo for several days and will retry and see if it works.

Thanks anyway
[HD2 Android NAND Development] despy1989:
Please check the flash.cfg in the recovery folder that you are using. I have had the same problem and realised trawling thru the forums the problem was with the second line in flash.cfg file

misc ya 1M

recovery ya|ro 5M

boot ya|boot|ro 8M

system ya 140M

cache ya 30M

userdata ya|asize|hr allsize

Instead this line should read

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

changing this sorted the problem

hope this helps
[HD2 Android NAND Development] zach.antre:
hmmmm... Strange...

Here is what happened to me.

I flashed cLK 1.3.3. and then the CWM 3.0.1.9. Everything works fine even CWM menu shows cLK1.3.3. CWM 3.0.1.9.

I then flashed TyphooN's ROM and the Kernel provided in 3rd post and everything is working fine.

I tried to use ROM Manager to check how good it was working. Then i tried "Flash CWM Recovery" in ROM Manager menu. I was messing around and decided to download the CWM for ZTE-Blade which is 3.0.1.4. (for testing purpose and not because i am stupid :p )

Now the strange part is first of all ROM Manager didn't recognise the version of CWM i am using, 2nd that it allowed me to flash a CWM recovery that is not for my device (but thats ROM Manager bug and Leo is not supported yet), and 3rd even though it booted in CWM the title was cLK 1.3.3. CWM 3.0.1.9 it was acting as CWM 3.0.1.4 (i just tested the charge feature and just keep rebooting after i shutdown)...

Also once i reflashed with fastboot the new CWM recovery 3.0.1.9. it were still acting as CWM 3.0.1.4.

I don't know it this is cLK or CWM bug but this is the right place to post it...
[HD2 Android NAND Development] seadersn:
for first: rom manager doesn't seem to be able to see the real version installed, it only stores the info of the recovery which it installed itself.

for second: not a bug ;) if rom manager doesn't correctly recognize your system, it lets you choose a recovery; no matter if it's suitable, you can flash any version. if your device gets recognized, you have only one choice: your device :)

for third: acting like means? did you shut down your hd2 and (after waiting 5 seconds) then plugged your a/c adaptor in?

then

it will be charged, led = orange means charging, green = full, blinking = overcharge / -heat; this doesn't work in recovery itself. :(

and reboot to recovery isn't working? that's related to the correct combination of cache partition size, initrd.gz (mounting of cache; evtl. corrected through an init.d startup script) and kernel.
[HD2 Android NAND Development] Stephen:
I have jsut tried the charging in off line mode and also finding that it is not working. I have the euro 576mb version with magldr 1.13 and 3.0.1.9 installed. Did as you suggested powered off the phone, waited 5 seconds and plugged it into the mains. It started to charge but simply turned back on again.
[HD2 Android NAND Development] seadersn:
charging in offmode is cLK only ;) magldr doesn't offer this feature.
[HD2 Android NAND Development] zach.antre:
ok... That's nice to know that those are not actually bugs... so i guess it will be fine once ROM Manager supports HD2.

Well about the "acting"...

The CWM version i flashed from fastboot was the 3.0.1.9.

The CWM version i flashed from ROM Manager was the 3.0.1.4. (ZTE-Blade)

What happened is that even though i reflashed 3.0.1.9 (and thats what the CWM Title were saying) the telephone for some reason kept the 3.0.1.4. (I have only tested the charging while phone was off - waited about 10 sec and then once i plugged in the cable turned on by itself)

3.0.1.4. was working fine btw.
[HD2 Android NAND Development] silverwind:
I checked it, and it is already correct (the green sentence above) as it should be (because I didnt do anything with the file since I downloaded from the original thread (Raider x)).

Thanks for your suggestion anyway:)
[HD2 Android NAND Development] despy1989:
Please can you list the exact procedure u followed including the Rom ur trying to use and also post the flash cfg info. I can try and help. PM me all this if you like
[HD2 Android NAND Development] seadersn:
@ despy: here is his thread about this issue http://xdaforums.com/showthread.php?p=12233670
[HD2 Android NAND Development] despy1989:
@seadersen & silverwind

I have responded with my suggestion on the thread please have a look. Sorry to hear about the problems.
[HD2 Android NAND Development] silverwind:
Yes, I replied in my thread.

No problem, and thanks :)
[HD2 Android NAND Development] seadersn:
updated...
[HD2 Android NAND Development] zach.antre:
seadersn i think you should fix the version names because it's a little confusing.

This is CWM v3.0.2.4 that's all, there is no need for the extra v1.4 that you have in title

Just add some info like.

YES/NO fixed

for cLK v1.4 (is out?)

for MAGLDR v1.3
[HD2 Android NAND Development] seadersn:
hmm, these are bothering me, too :) thought, some ppl want this kind of "status".
[HD2 Android NAND Development] seadersn:
completely removed the silly version numbers; you're right :) they were annoying.
[HD2 Android NAND Development] pongster:
Nice one! Any chance Reiserfs support for Nandroid can be incorporated? Not sure if its just a few configs to be set for the support, but It may be possible. :)
[HD2 Android NAND Development] UNOPARATOR:
Thanks for your efforts. A quick suggestion, you should make Post#2 in descending date order so that it would be easier to see the latest changes at the top of the post. :D
[HD2 Android NAND Development] birkoffsjunk:
Here is ClockworkMod Recovery 3.0.2.4 as a flashable zip ;)
[HD2 Android NAND Development] seadersn:
@ pongster: contact me, let's do this together ;)

@ unop: done :p

@ birkoffsjunk: linked your post in opener :) thx!
[HD2 Android NAND Development] pongster:
PM me your email ;)
[HD2 Android NAND Development] Kameirus:
can anyone tell me what size the new clk cwm is

is it 140 or bigger

as i am using Typhoon cm7

Thanks
[HD2 Android NAND Development] xing7ba:
thank you!!
[HD2 Android NAND Development] seadersn:
here you've got sth wrong :) cLK supplies the partition layout, not cwm; it never does, in magldr times cwm was flashed with the daf flasher, which partitioned the nand in our beloved hd2's. cwm is a independent, flashable program / "miniandroid", if one wants to see it this way.
[HD2 Android NAND Development] raven_raven:
But TyphooN CM7 uses 130M system, this is 150M system recovery. Is there a way to resize it or it's not needed?
[HD2 Android NAND Development] arif-ali:
You shouldn't need to resize, 150M leaves you with ~ 20M, just in case future releases grow, you don't have to keep flashing cLK

so 150M should work fine for you
[HD2 Android NAND Development] raven_raven:
I understand. Thanks.
[HD2 Android NAND Development] Kameirus:
ahh ok had noobish moment lol

Thanks
[HD2 Android NAND Development] enrierosi:
The same for me with the last 3.0.2.4 version..... Any help? :(
[HD2 Android NAND Development] tobiascrystal:
CWM does not fix the issue with the charging in MAGLDR ony CLK. they work completely different, yet the same.
[HD2 Android NAND Development] arif-ali:
seadersn,

another one for the OP,

Off mode charging only works with cLK 1.3.3 and above

Off mode charging will not work with MAGLDR, until DFT enable/fix the issue
[HD2 Android NAND Development] zach.antre:
I think a config file for partitioning in cLK (like the config of CWM in MAGLDR) is necessary. That way there is no need for people to compile new cLK for using with different roms.

One more benefit is that we could also avoid confusion with different cLK partition tables etc, since i have noticed that not many people, even ROM developers, were aware of that (that partitioning is controled by cLK and not CWM).

Seadersn i guess you can talk to Cedesmith about that :)
[HD2 Android NAND Development] seadersn:
he said one time, that sort of editor for the .nbh @ could be programmed. there are some ppl, who are able to program such thingy; they could help him and/to do it or maybe any time an editor gets written by him.

but that's cLK stuff :) he said it already, yuo can question him about that and the status :D

@ arif: jep, good thought.