yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Petulinek:
But if you have some ext partition, formatting doesnt erase it, doesnt repartition SD card to have only one FAT-32 partition, only format FAT-32 SD partition, isnt it?
[HD2 Android NAND Development] karendar:
Does backup and restore work on cLK though with your build? I imagine your CWM was compiled with cLK in mind, so the images created by the other CWM won't work and vice versa.
[HD2 Android NAND Development] seadersn:
sure :) but you have to have in mind that the boot partitions have different filesystems (beside the fact that one needs a patched kernel anyway). in magldr it's yaffs2, in cLK raw; recovery partitions are raw in both magldr and cLK, therefore there shouldn't be a problem to use it on both sides.

i've restored my data partition from magldr without any errors, after flashing recovery, wiping data / factory reset as cedesmith stated in his thread (for formatting the userdata partition, so that it is initialized and writeable) and then the rom-zip.
[HD2 Android NAND Development] mattfmartin:
Just wondering why it says this in the main screen of recovery?

E: can't find misc

E: can't find misc

E: can't find misc

everything works. was just wondering what thats all about?
[HD2 Android NAND Development] seadersn:
it's the missing misc partition, which is useless atm and wasn't compiled into the cLK image or added to the MAGLDR partition layout you have flashed :)
[HD2 Android NAND Development] mattfmartin:
Ahh ok, thanks for clearing that up;p
[HD2 Android NAND Development] seadersn:
:D np :)

according to cedesmith this will be added into cLK so that for example reboot to recovery or the rommanager can be used.
[HD2 Android NAND Development] mattfmartin:
Nice, after that's implemented, it WILL be a native device.;p
[HD2 Android NAND Development] karendar:
As close to a native device we'll get, indeed... Charansingh will just need to complete the aosp kernel
[HD2 Android NAND Development] 4D3:
Hi,

Just installed this using the 400mb setup from raiderx and i still have the 3.0.0.5 showing and nothing has changed regarding the number of "no" showing...

whats going on? i did:

download 400mb layout from raider thread

downloaded:

put the *.img from

into

400mb layout from raider thread

booted into USB flasher mode and installed as per Raider thread....

Why do i have 3.0.0.5 showing? do i need to place something different into my sd card?

Thanks in advance?

MG
[HD2 Android NAND Development] 4D3:
Done this 3 times now and i still have 3.0.0.5 and all the no's showing....

anyone fancy posting a working 400mb partition layout?

thanks in advance

MG
[HD2 Android NAND Development] Dasf77:
Have you renamed the 3.0.1.4 to recovery-raw.img inside the folder before flashing?
[HD2 Android NAND Development] af974:
hehe, no problem seadersn, i can confirm that make a backup/restore in 3.0.1.4, does sort the same effect as a backup from 3.0.0.5 and restore with 3.0.1.4.
[HD2 Android NAND Development] hessamx:
i have the same problem ,i change the name and but still 3.0.0.5 !!
[HD2 Android NAND Development] af974:
There is no need to rename it both have the same name.

Try with 390 system partition.
[HD2 Android NAND Development] hessamx:
what is the 390 system partition ?
[HD2 Android NAND Development] af974:
You can change the "flash.cfg" as you wish, just open it with a notepad app:

misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 390M
cache ya 4M
userdata ya|asize|hr allsize
[HD2 Android NAND Development] Dasf77:
Hum, tried it myself and worked ok. I assume you are in Magdler.

Download this http://cl.ly/0i3b1N1o0L261m3n0R1C and then flash it. It has to work.
[HD2 Android NAND Development] hessamx:
is dosen't work ,still 3.0.0.5 !

i dl it and flash ,But still 3.0.0.5 !
[HD2 Android NAND Development] af974:
Do you got some kind of output error?
[HD2 Android NAND Development] 4D3:
no the recovery-raw.img is named as "recovery-raw.img" and i have this in my flash.cfg:

misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 4M
userdata ya|asize|hr allsize

can you help? I still have 3.0.0.5

MG
[HD2 Android NAND Development] tommyhui:
i get these messages after used flash_image recovery command:

and i can't boot it into cwr...

what can i do now?? and what path with the image storage?
[HD2 Android NAND Development] seadersn:
jep, that's right :( for complete cleaning up of sdcard there's another possibility, but available only in magldr:

- go to "10. services" menu

- choose "5. clearsd mbr"

this erases every partition on sdcard; after that one can format it as usual per pc or in clockworkmod.

for clk users it's necessary to clear the mbr of the sdcard on a pc.

hmm, anyway, partitioning w/ 'sdext size 0' is creating an ext-partition on sdcard.

let's look at this, maybe it's possible ;)
[HD2 Android NAND Development] podezebi:
Hello,

I can't use "8. AD Recovery" ... I get a Kernel Image error...

Anyone to help me ???

please ;)
[HD2 Android NAND Development] seadersn:
jep, classic "recovery partition too small" case :( sry, you have to reflash clockworkmod together with the partition layout suitable for your rom. you can do a backup of your rom in android itself; but it's very long-winded process. i'm describing / explaining this only if it's really absolute necessary...

or you simply reflash the 3.0.0.5 recovery with "flash_image" as described in first post. you have to download a partition layout from raiderx's post, take out the "recovery.img" file and copy it to your sdcard. then proceed with the steps @ 1st post :) but reflashing w/ this new recovery makes more sense. jep, time consuming, but... ;)

all this assuming you are running magldr; cLK does have the correct recovery partition size.

i believe, your recovery partition is too small, too ;) i've tested it with magldr and it's working; either the flash_image method or the cwm zip file.
[HD2 Android NAND Development] tommyhui:
i would like to know if there enough space from cwr 3.2.0.0 to 3.2.0.1?

my bootloader is magldr...
[HD2 Android NAND Development] podezebi:
but i can access to recovery with the old method (2. SD boot) ...
[HD2 Android NAND Development] seadersn:
tommy: jep, space should be sufficient. how did you flash 3.2.0.0? with DAF.exe and together with partition layout? if, what is the line containing "recovery" in flash.cfg saying redarding size of partition? "filesize" or "5M" or sth else? change the partition size to "5M" or maybe even "6M" (w/o the "") and flash again, please. then there will be no more stress with new recoveries ;)

podezebi: yes, of course, sd version should work in any case and can be used for backing up your current android build and configuration; i forgot this possibility...
[HD2 Android NAND Development] podezebi:
ok, i'll try to increase recovery ! i hope it will work (i flash with many parameters, but it didn't work)

thanx
[HD2 Android NAND Development] tommyhui:
thank you, seadersn

the problem solved^v^
[HD2 Android NAND Development] seadersn:
yay, i like this :D ^v^ hrhr.

k, happy i was able to help out :)
[HD2 Android NAND Development] davidwxh:
I flashed the CWM 3.2.0.1 form 3.2.0.0. But cant use "8. AD Recovery" display: ERROR:ERROR:Invalid boot image header.:eek::eek:

I use 150M sys and 44m cache.

What happen? How to fix it?

Sorry for my bad english.
[HD2 Android NAND Development] chris10230:
seriously read up the last 10/20 posts you will find the answer, its that you need to increase the space for recovery in flash.cfg ....
[HD2 Android NAND Development] :
I know, but sometimes I switch between roms that require sd-ext and some that don't. I already know about 'format /sdcard" but sometimes I want to completely delete the ext partition..
[HD2 Android NAND Development] arif-ali:
CWR 4.0.0.0

Here is an updated recovery

Highlight of this recovery is that now we can use tar files as well as zip files, and it has support for /data/media
[HD2 Android NAND Development] seadersn:
holla... a new recovery this soon... k, i will update first post :)
[HD2 Android NAND Development] Olioaglio:
Noob questions upcoming

seadersn, please could you give me some hint...

ATM i am running raf4.02 with Magldr1.13 and CWM 3.0.0.5 with 400M data.

As far as I read before I would have to repartition to be able to use CWM 4.0.0.0 because of larger size. Lets say I would take the DAF/img version of 4.0.0.0 in 1st post and reflash NAND I would have to to rename "recovery_4.0.0.0_leo.img" to "recovery-raw.img", replace it in the CWM 1.3 folder and edit the flash.cfg inside as following:

Is this correct/valid?

Second question: The current cache size of my 400M flash.cfg is 4M.

Is a larger Cache Partition (e.g. 10M or 20M) a benefit)

Third (and most important) question: If flashing/repartioning would succeed, could I enter the updated CWM 4.0.0.0 and fully restore a CWM 3.0.0.5 Nandroid backup I made before repartitioning? Or would this fail because of resize and I had to restore only using Titanium?

Your reply would be highly appreciated... Sry for noob questions.

Cheers, Olioaglio
[HD2 Android NAND Development] illuzi0n:
EDIT: nvm fixed the issue :)

ps: thanks seadersn and arif-ali for the hard work
[HD2 Android NAND Development] agormog:
Why cant I flash the newer recoveries from within ROM Manager? It just says 3.1.0.0 is still the newest version
[HD2 Android NAND Development] deano309:
Because that is the newest version that Rom Manager recognises as being compatible with the HD2?!
[HD2 Android NAND Development] dabezt:
Hiya my friends, first of all thnx for this great job!

Is it possible to do a 'selective' Backup with Recovery for MAGDLR? I've a huge folder with music & docs in /sdcard and I don't want it to be backed up...

Thnx! Cheers!
[HD2 Android NAND Development] seadersn:
@ olio: magst du nudeln mit knoblauch? :D gute wahl :) but btt: all you've written is correct; these are the complete steps which are necessary, yes. regarding restoring the backup with 4.0.0.0, backed up with 3.0.0.5: it should work, without problems. resizing of recovery partition won't disturb the backup / restore :) it's system/userdata (sd-ext)/boot partition sizes which are relevant. these stay @ same size @ reflashing the new layout with bigger recovery partition.

@ agor / deano: deano is right ;) koushik only didn't update the new recovery for hd2 in rom-manager. btw. the changes (/data/media support and tar file-format @ backup / restore) aren't relevant for our hd2's, only for motorola xoom.
[HD2 Android NAND Development] seadersn:
sd-card itself isn't backed up :) it's boot/system/userdata/recovery/cache/sd-ext partitions and the /sdcard/.android-secure folder on sd-card.

nevertheless a selective backup (regarding partitions) would be a nice feature, yes... we will see what time will bring to us.
[HD2 Android NAND Development] ksubedi:
Updated HD2 Toolkit with the latest recovery, good job guys :) I really like the yes no patch :D
[HD2 Android NAND Development] dabezt:
Thnx for the answer... I've tried again and you're right (of course :-)) I was confused about seeing /data/ folder being backed up...

Cheers!
[HD2 Android NAND Development] TOMLEOUF:
Somebody can help me with that?
[HD2 Android NAND Development] arif-ali:
Yes use the CWR update that has been provided, you can use that within recovery to flash a new recovery
[HD2 Android NAND Development] TOMLEOUF:
I tried to update that way... but I got an error which made my recovery unsuable... and now I get to use the SD recovery 3.0.2.4

I've done a reserch on that topic and I found that I have to change the flash.cfg or something in order to set a bigger cache... anyway I can't flash anymore and Now I can't use the recovery :'( except from my SD card!!

Help
[HD2 Android NAND Development] seadersn:
not cache: recovery ;)
[HD2 Android NAND Development] Olioaglio:
Thx for pointing this out, m8. :cool:

Regarding my the second question about sense of a larger cache partition (default in flash.cfg is 4M, why not 10M or even 20M if there's space left?) any suggestions? Just wondered, because on Leo512 usable NAND is 445MB, so a larger Cache Partition than 4M would be possible, but don't know if this makes any difference anywhere :confused:

Cheers, Olioaglio
[HD2 Android NAND Development] Dreammaster:
restore of sd-ext failed all the time... with version 4.0.0.0 back to 3.2.0.1 here the full restore works..
[HD2 Android NAND Development] seadersn:
that's strange; looks like nothing changed what would cause this. i'm using this recovery and all other functions are ok; but i'm not using this sd-ext stuff ;) it's a phone, not a game console :D but for some roms sd-ext is necessary, unfortunately :(
[HD2 Android NAND Development] TOMLEOUF:
When I try to update the cwr from the flashable zip file I get this message... why can I do? Just remember that I can't use MiniUsb port.... :O
[HD2 Android NAND Development] seadersn:
if usb port is broken: from now on only sd variant :(

best would be to flash original winmo image via sdcard and send it in to htc for repair. you've got guarantee left?
[HD2 Android NAND Development] yuhenyo:
do i just use the customruu.exe in flashing the clk 1.4.0.1 layout?
[HD2 Android NAND Development] arif-ali:
Yeah, that's right
[HD2 Android NAND Development] tmihai20:
To my shame, I didn't realize until yesterday that I can flash recovery through recovery :) I never thought of what the CWR package was about. I just flashed it yesterday and it went well :) Thank you for being our shepherd for us and keep up the good work :)
[HD2 Android NAND Development] tmknight:
Default action = No

Great work, I imagine the idea of multiple "No" before getting to "Yes" was to help avoid unintended action (e.g. hitting Yes when you didn't want to). I prefer one of each as you have implemented :thumbs-up:

However, defaulting to "No" would be preferred (at least by me to help avoid unintended action), is there a way for this to be changed on the user side or could we take a poll as to which option the community desires (default yes or default no)?

Cheers!
[HD2 Android NAND Development] SlyRder83:
after flashing the zip my recovery stays the same 3.0.0.5. What am i doing wrong?
[HD2 Android NAND Development] TOMLEOUF:
No guarantee left... it's too expensive to repair so I just deel with it...

When I try to use sd file 4.0.0.0. My phone just shuts down as soon as I clique on AD SD...
[HD2 Android NAND Development] arne182:
I have the same on mine.
[HD2 Android NAND Development] Kameirus:
just so you know 4.0.0.0 does not play well with the new sense 3.0 roms

had to go back to 3.0.2.5 to get the rom to install properely and load up

i dont know whats causeing it but ive seen it talked about by others also
[HD2 Android NAND Development] arif-ali:
CWR 4.0.0.2

Updated to latest version on github

enjoy!!!
[HD2 Android NAND Development] mwakious:
hizzz,i tested 4.0.0.2 on cLK,finally its working good,with 4.0.0.0 i had issues with partitioning and restore,this version works good.

good job
[HD2 Android NAND Development] chshrm:
Thank you friend, great jop, will give more test:p
[HD2 Android NAND Development] siddharth singh:
Hey arif... What changes in this version :P
[HD2 Android NAND Development] slbenz:
Tried loading the CWR zip file from the OP and now when I go to MAGLDR to 8. AD Recovery or 1. Boot WPH both say WPH not installed. Anyone can help me correct this? Tried updating without realizing that I didn't have the most up to date CWR on board. Used ROM Manager to update but still didn't work. Any suggestions would be greatly appreciated.
[HD2 Android NAND Development] slbenz:
Well it looks like I found the problem. Needed to reflash the correct partition to my ROM and restore. Back to CWR 3.0.0.5 for me since it was working fine before trying for an update.
[HD2 Android NAND Development] mwakious:
issue for me to...the restore,i cant restore any backup with 4.0.0.0 and 4.0.0.2

edit: found another:off line charging,it charges for 3-4 minutes and then it stops and the red light is blinking
[HD2 Android NAND Development] chshrm:
me too, 4.0.0.0 and 4.0.0.2 can not restore sd-ext, but if you choose restore advanced option, you can restore each part individually. hopping improvement soon.
[HD2 Android NAND Development] Yom:
No MD5 generated on nandroid backups under 4.x

Hi arif,

First off, LOVE your work, thank you.

I noticed yesterday that CWM 4.x doesn't generate the MD5 sums (Just creates an empty file) for the nandroided IMG files, and therefore they cannot be restored.
[HD2 Android NAND Development] arif-ali:
thanks for this, will have a look soon
[HD2 Android NAND Development] :
+ 1

Can confirm this, there is definatly a problem. Advanced restore works perfectly.
[HD2 Android NAND Development] MarkAtHome:
I, too, tried Advanced Restore, choosing only DATA, it looked like it was restored, but upon bootup, my data wasn't there. :eek:

FWIW, I am using v4.0.0.5, dated today...
[HD2 Android NAND Development] arif-ali:
hmm, I was just going to say, that 4.0.0.5 is out, and if people could test from the below link

http://db.tt/pbIEuSE

but it seems you have tested already, and you still are having similar problems.

Been a bit busy lately, so haven't been able to update as often, and looking at the md5 checksum issue
[HD2 Android NAND Development] criszz:
+1 v4.0.0.5 same problems + tried to restore old vers on backup with md5 but just formated my sd-ext and no restore.
[HD2 Android NAND Development] seadersn:
for me every 4.x.x.x recovery seems to be broken with our hd2's. 4.0.0.5 for example does not backup at all. i'm using 3.2.0.1 for now; it works rock solid and stable :)
[HD2 Android NAND Development] dermeister20:
Please can you uploud 3.2.0.1 for clk?
[HD2 Android NAND Development] seadersn:
http://xdaforums.com/showpost.php?p=14516953&postcount=574

available some pages back ;)
[HD2 Android NAND Development] dermeister20:
thx for help :)
[HD2 Android NAND Development] MarkAtHome:
Understood, Arif, and thanks for all the time and effort you have put into this.

I have experienced an issue that could simply be a result of a lack of knowledge on my part. I wiped my device & SD card yesterday, did a Task29, MAGLDR, flashed 4.0.0.5, and installed the latest TyphooN CM 3.3.7.

I rebooted to Recovery, noted that 4.0.0.5 was there, then rebooted to the ROM.

I clicked on ROM Manager Premium, which informed me that I needed to flash CWR, so exited that, again rebooted to Recovery, and was able to assure myself that I still had 4.0.0.5.

Returning to ROM Manager, I thought "oh well", and agreed to have it flash CWR. I am left with 3.1.0.0! :confused:

Would you tell me the connection, if any, between CMR and ROM Manager?

What is it that I am not understanding?
[HD2 Android NAND Development] criszz:
rom manager install for you cwr, but last version of cwr in his data base is 3.1.0.0. . now u can flash latest version but rom manager will show 3.1.0.0. don't press flash cwr again in rom manager.
[HD2 Android NAND Development] :
Restoring sd-ext fails after downgrading cwm.

Yesterday I downgraded my cwm from 4.0.0.2 to 3.2.0.1 because of the issue that complete restoring doesn't work as described few pages ago.

..but then I wasnt not able to restore my sd-ext: "error while restoring sd-ext"

Upgraded to 4.0.0.0 then, but same error.

I recreated my sd ext again...without success, still same error.

Updated to 4.0.0.2 again and now it works.

..so somethin is messed up there.

Is that a known problem that the different cwm version are incompatible?

Sry if that is a known problem or discussed before, didn't read about that.
[HD2 Android NAND Development] MarkAtHome:
From what I gather (I cannot assure anyone that it is, indeed, fact), Koush takes the then released CWR and patches it so that it contains a hook to ROM Manager.

It looks like that versions not patched, will not be seen by ROM Manager.

I think that ROM Manager should be able to read the system and determine which version, if any, of CWR has been applied, if it is newer than what ROM Manager "knows" about, accept the updated version and add the required hook to ROM Manager, otherwise prompt the user to flash the version of CWR that it knows about.

There is too much dependence on ROM Manager having the latest CWR on its own.

Consider that Koush has a life and does not spend all his time checking to see what updates others have put out there. Enabling ROM Manager with the capability to update itself, pertaining to CWR, would be beneficial to both Koush and his fanbase.
[HD2 Android NAND Development] seadersn:
jep, mark, this would be the best option for all: reading the header of recovery and compare with the version offered @ RM. if v.no. smaller than offered one @ RM, then possibility of choice to flash or not would be nice.

interesting... this reads like: "when sd-ext is created, backupped and restored within one single version of cwm it doesn't cause problems. but when created with a particular version of cwm and trying to backup/restore with an older / newer one it does."...?
[HD2 Android NAND Development] jjrumph:
OKay so I too have determined that 4.0 and 4.02 dont seem to restore properly. I backuped some apps and it looked like they backed up fine but when I restore they just boot loop. So I'm guessing that is the problem.

My question is since I have 4.o clockwork is there an easy way to go back to 3.2. Tried flashing the 3.2 CWR zip but it aborted.

Guessing there is another way.
[HD2 Android NAND Development] clyder:
I reverted to 3.2.0.1 with terminal emulator. I always install recovery that way.

Place .img file in, for example, root of sd card and in terminal emulator type:

su

flash_image recovery /sdcard/nameofthefile.img
[HD2 Android NAND Development] jjrumph:
Well I try that and all I get is image not found.it's there for sure.

Maybe a zip flash will be available to update 4.0 soon. I'll keep trying.

EDIT: well i managed to get back tyo 3.0.0.5. Now to get back to 3.2
[HD2 Android NAND Development] tmihai20:
Flashing recovery this way doesn't work if the file you are trying to flash is larger than the old one. I tried to flash recovery 3.2.0.1 over 4.0.0.2 using the CWR files from within recovery and I couldn't get into recovery anymore. I used your method and there were some errors while flashing. Then I thought I should compare the 2 files, the older recovery file is larger than the new one. I hope I didn't screw up my installation, because I didn't back it up.
[HD2 Android NAND Development] clyder:
I had the issue with size at one point, but I flashed partition layout file with 5M tag instead of filesize tag for recovery and flashed all other recovery version via terminal emulator.

If your recovery is broken now becase of the size issue you can use the same method to flash some older version of recovery, I cant remember which one was small enough, I think it was 3.0.x.x. something. When you succeed in doing that you can backup your rom, and then you should flash the recovery you want via DAF with changed flash.cfg with fixed size for recovery. After that you can use terminal emulator to flash recovery directly from android without the size issue to worry about.

Are you on magldr or cLK?