yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] tmihai20:
Well, I managed to update to the latest version of Spirit FM app, only after installing aLogcat to try to get a logcat on the problem. My phone restarted the first time, but the phone booted just fine. Then I tried to update that app while aLogcat was running in the background and, to my surprise, it updated without problems. I think the new market needs to be more polished, I never had any problems like this until now. Not a single problem. This one app gave me headaches. It's all sunny now (although it's pitch dark here in Romania). I wanted to see if somebody else had this problem before. Thanks for the reply.
[HD2 Android NAND Development] pyrorob:
hello, i was wondering if anyone could help, i need to modify the initrd of cwm to recognize a new partition and i cant unpack the img myself to edit it, would anyone be able to lend a hand to unpack/repack it, or at least provide some details on how to do it myself.. i already modified teh android os and initrd im using in the kernel im using to reognize it, but if i can get cwm to work with it, im stuck using magldr to install data to teh partition, thanks.

so i found that cwm will mount the partition based on teh commands in the script alone, since mtd does see it. i cant mount/unmount or format from the cwm interface, but regardless, this is good..
[HD2 Android NAND Development] famewolf:
As a magldr user my one question is what additional option/features is the 5.x version going to give me over the 3.2.x version I already have installed?

I don't see anything in the changelog in first post listing new features.
[HD2 Android NAND Development] luba6ky:
i installed the new CWM and works fine ...

thanks, seadersn
[HD2 Android NAND Development] arif-ali:
You can use the unpackbootimg to extract it. This will give you the kernel and the initrd. You can modify the initrd as normal and then you can recreate the recovery.img by running the following command

mkbootimg --kernel kernel --ramdisk initrd.gz --cmdline "no_console_suspend=1 wire.search_count=5
" --base 0x11800000 --output recovery.img

I hope that helps
[HD2 Android NAND Development] pyrorob:
thanks, i was able to modify and repack a recovery img, the only thing thou.. see i have a partition called "sysapps" with the modifications ive done, it shows under mounts and storage with teh option to be able to format it, but theres no option present to mount.. anything i can do, short of compiling a new cwm? i think all i would have to do is add the mount point (mtdblock4) to the fstab file, but its nowhere in the extracted files, does the kernel create it? thanks.
[HD2 Android NAND Development] imfloflo:
Thanks for this awesome recovery.

I would like to know if this lastest version is compatible with the "reboot to recovery" option in MIUI rom on HD2.

I'm currently using a 4.0... version and it doesn't work with this version.

F.
[HD2 Android NAND Development] ogonzuhnina:
If U want this to work switch from MAGLDR to cLK

cheers
[HD2 Android NAND Development] imfloflo:
@ogonzuhnina ok thanks, but i tought this was workng in CWM 3

and for information: can i switch easyly from MAGLDR to CLK without wiping my rom current settings?
[HD2 Android NAND Development] J.Soko:
Hello,

It works with Lady Miui CLK

http://xdaforums.com/showthread.php?t=1028693

but not with MAGLDR.

No, and it shall be better to do a task29...

Ciao,

Joachim
[HD2 Android NAND Development] clyder:
I did it once without issues.

- do a backup of your rom in CWM.

- flash cLK and recovery (task29 is recommended I guess)

- do a restore of the backup you did previous

- flash a cLK kernel.

I did that with Typhoons rom some time ago.
[HD2 Android NAND Development] imfloflo:
@J.Soko @clyder Thanks for quick and clear answers, i think i'm gonna wait for a CWM 6 with a fix ;)
[HD2 Android NAND Development] arif-ali:
@imfloflo, The reboot to recovery and bootloader only works with cLK, it has never worked with magldr. Once (if) cotulla updates magldr, and he adds the boot reson stuff into it, then it will work. It is nothing to do with CWM itself
[HD2 Android NAND Development] imfloflo:
@arif-ali ok thanks for this response, so i'll give a try to cLK

btw the link to 1.4.0.1 in your signature is not good >1.3.3
[HD2 Android NAND Development] clyder:
Use the second link in arif's sig that says "cLK 1.4.0.1 all partitions 80-450"
[HD2 Android NAND Development] MarkAtHome:
Thanks for all your help, Seadersn. It has been appreciated.

If you are still here, can you tell me whether the above means that flash.cfg can be configured so that the system partition can now be flashed with either Reiser, NILFS, ext 2/3/4 filesystems?

If so, what would flash.cfg look like?
[HD2 Android NAND Development] Realalist:
And let's just say you don't have 3.0.3.5 and AD Recovery stops working in MAGLDR, what should you do to fix it and get the update?

---------- Post added at 03:17 PM ---------- Previous post was at 02:54 PM ----------

For any noobs following the nand instructions and it not working just download the third file and use recovery to flash from zip and do it from there. I've been working with this for three hours and finally got around to doing it that way and it was as smooth as my ROM.:cool:
[HD2 Android NAND Development] arif-ali:
copy the img file onto phone in android i.e. /sdcard using adb push

use "flash_image recovery recovery.img" to flash the recovery

reboot and use AD recovery
[HD2 Android NAND Development] Realalist:
Thanks.
[HD2 Android NAND Development] bondocel:
Help guys, i just can't get this right, i cannot install this recovery partition, i get "invallid boot image header" and i used this configuration in flash.cfg :

misc ya 1M

recovery rrecov|ro|nospr 5M recovery-raw.img

boot yboot|ro 5M

system ya 180M

cache ya 5M

userdata ya|asize|hr allsize

-What am i doing wrong
[HD2 Android NAND Development] seadersn:
nothing; maybe bad blocks in that part of nand memory. try increasing boot partition to 7mb :)
[HD2 Android NAND Development] Elmar1801:
sd-ext restore with ReiserFS still won't work.

sd-ext.img not found.
[HD2 Android NAND Development] seadersn:
that's because the kernel with which this recovery was compiled doesnt support this filesystem :(

geiler nick xD passt ja grad ganz gut höhö
[HD2 Android NAND Development] Elmar1801:
???????????????

Warum stehts dann hier. Jetzt muss ich zurück auf eine ältere Version da ich ein wipe gemacht hatte.
[HD2 Android NAND Development] seadersn:
weil das im startpost noch nicht geändert wurde; arif nutzt einen anderen kernel zum compilen als ich ;)

he: why is it written in first post when not supported anymore? need to get back to an older version cause i did a full wipe :(

me: because it wasn't changed @ first post / not checked by me if arifs kernel used for compiling recovery is supporting reiserfs etc. maybe he's using another kernel than me for comp. recovery, which hasn't reiserfs enabled.

is this the case, arif? :D
[HD2 Android NAND Development] cmhtcleo:
reiserfs is supported in the kernel sd-ext is an issue at the moment with v5 of the CWM. The CWM code needs to be looked at to get it working. I will have a tinker later
[HD2 Android NAND Development] seadersn:
ok; so it's the tar vs img problem :( very good that i'm not using sd-ext... :) selfish itm, but... :D
[HD2 Android NAND Development] runnin-low:
Ok not sure what's going on but after I copy recovery raw img ..reflash the partition nothing happens??

then when i go into ad recovery this error comes up:

error error invalid boot image header???

when i look at the version of my cm recovery is v.2.5.1.8 what am i doing wrong?

any help would work

BTW would anyone have a different copy of the zip in a different form i cant seem to download them...on this computer..thanks a bunch again
[HD2 Android NAND Development] knifeproz:
I have this problem too. What i did to fix it is i downloaded a file and put it on the SD card in a folder. it had the recovery on there. so instead from AD recovery i use AD SD - i think the 3rd option or so, so then it boots from the sd instead. i do wish i can solve the problem the regular way though because i cant seem to be able to clean dalvik cache and some other things...(can't update CWR)
[HD2 Android NAND Development] tsddave:
I am using magldr 1.3 and currently have the v4.0.0.0 version of cwm on my phone.

When I do a backup using cwm and reboot my phone I find that it knocks out my sim card and then I have no signal and ofc then cannot use the phone for calls or sms. The only way to correct this is to do a full wipe and reinstall. Flashing the rom back over like an update doesnt change this.

I have used cwm on my other Android devices with no issues ever.

Anyone know what might be causing this issue?

Also I have downloaded this newer version of cwm, can I simply flash the zip using my existing version of cwm?

UPDATE:-

I flashed over the old version and everything is fine now.
[HD2 Android NAND Development] BoneMo:
CWM serious problem

i have cwm 5.0.2.6 and have strange problem....when i select option flash .zip from sdcard....recovery is not able to see .zip files ?? what to do ?
[HD2 Android NAND Development] arif-ali:
Have you scrolled down, sometimes the bottom is cut off. Please try again

Edit:

I have also updated 5.0.2.7, in the nightlies; There was a bug in the 5.0.2.X series where the boot.img wasn't being flashed correctly; which is now fixed.

I will have a look at the sd-ext issue in the next few days
[HD2 Android NAND Development] arif-ali:
I have just tried doing a backup and restore of my rom, after installing dtapps2sd and moving dalvik and data to the sd-ext (uurghh!!! don't like sd-ext).

and I managed to restore the whole ROM.

Can people test and try it.

If it doesn't work, please attach your /cache/recovery/last_log and /cache/recovery/log and the output of ls /sdcard/clockworkmod/backup/*/*; so that I can see exactly what the problem and errors are.

regards,

Arif
[HD2 Android NAND Development] clyder:
I had many backup/restores in 5.0.2.6 since I switch my ext from reiserFS to ext4. There was full restores and partial and there were no issues while doing so.
[HD2 Android NAND Development] Macelangelo77:
Just one quick question for arif-ali: When browsing your dropbox I see the last nightly build (currently recovery_5.0.2.7-20111118_leo.img). Is this the same file as recovery_5.0.2.7_leo.img? Is this file always pointing to (or the same as) the latest nightly? Or is it the first release of a new series?

Thanks in advance.

Sincerely,

Mac
[HD2 Android NAND Development] arif-ali:
The nightlies are true nightlies, so anything that is along the line

recovery_<version>-<date>_leo.img

anything else is something that is done weekly on a Sunday for those who want the CWR, sd builds
[HD2 Android NAND Development] Hahutzy:
---deleted, newest CWM can be navigated without volume buttons
[HD2 Android NAND Development] Hahutzy:
Hey guys,

I'm on cLK 1.4.0.1 and I flashed CWM 5.0.2.6

Is there a reason why when I'm scrolling up with Home button and scrolling down with Windows button, the menu disappears?

Somehow this is happening (not actual code!):

if (key_code == KEY_MENU) {
if (visible) {
visible = 0;
action = HIGHLIGHT_DOWN;
}
else visible = 1;
}
else if (key_code == KEY_HOME) {
if (visible) {
visible = 0;
action = HIGHLIGHT_UP;
}
else visible = 1;
}
[HD2 Android NAND Development] ShironLive:
Is it possible to install the new ClockworkMod Recovery without using the usb port, when using NAND ?
[HD2 Android NAND Development] TheInVisibleGoD:
Of course... just download and flash with ROM Manager!
[HD2 Android NAND Development] mdskrzypczyk:
Because this is a recovery, not a rom

Sent from my HTC HD2
[HD2 Android NAND Development] MarkAtHome:
Hi arif-ali -- On occassion, for whatever reason, I go to restore a backup and get an MD5 mismatch. Any chance of including a module in CWR that either permits the user to have that checksum ignored or re-written?

What think you?

Would still love to see the option of CWR supporting additional filesystems beyond yaffs2... ;) ;)

Regardless, thanks for your hard work. I can live without it if it is something you cannot do.
[HD2 Android NAND Development] NYLimited:
You didn't by chance change the backup folder names to something that includes a soace, did you? CWR does not like spaces in the fikder name..

Check this post - it may be of some help with md5:

http://xdaforums.com/showthread.php?t=714114
[HD2 Android NAND Development] MarkAtHome:
There wasn't any apparent reason for it.

I would like to see an additional option, once in recovery, to review and fix any wayward backups with the option to run the backup regardless of the mismatch.
[HD2 Android NAND Development] AgeOfPanic:
This might sound stupid, but is the flash_img file really only 14 kb big? Somehow the 3.0.0.5 version is almost 4 Mb and this file is way smaller.
[HD2 Android NAND Development] seadersn:
flash_image is a binary, a command with which you can flash raw images; such as the recovery.img ;)
[HD2 Android NAND Development] Ashhong:
Hi guys...problem here. I made a boo boo.

I didn't read the instructions carefully and used the flash_image command and pointed terminal to the flash_image file instead of the img file. It did some stuff then errored out. I then tried to go to AD_recovery using magdlr and it gives me an error and I cant go in.

Then tried to go back to terminal and flash it correctly. Terminal says like "successfully wrote block at #####" then at the end said failed with error:-1. Any tips?
[HD2 Android NAND Development] pee-wee:
Download leo SD and leo CWR (page1)

Extract leo sd on root of sdcard, select ad sd on magldr menu, than flash leo cwr... If still error you need to task29, reflash magldr and reupdate cwr

Sent from RAF Menwith Hill
[HD2 Android NAND Development] Ashhong:
Thanks for the help. I actually was able to fix it just before you posted this by booting into Windows (usually on OSX) and installing CWM using the DAF.exe file. Now my only question is, how do I set the recovery partition size to 5mb as recommended? So that I can install through CWM.
[HD2 Android NAND Development] bigmark88:
Downloaded extracted n running smoothly..

Thanx
[HD2 Android NAND Development] pee-wee:
There is application called HD2 toolkit (runing on Windows OS) you can make partition using that...

But you must reflash cwr again, because it has built in cwr 4.0.0

Sent from RAF Menwith Hill
[HD2 Android NAND Development] AgeOfPanic:
Wow, I was complete of on understanding the instructions then ;). Anyways, after trying everything I reflashed it using 3.0.0.5 with a 5M recovery size this time and then used that to upgrade to 5.0.2.6. Now it works and it is nice and blue. Thanks.
[HD2 Android NAND Development] Hahutzy:
Hey seadersn and other devs, a couple of bugs:

1. When I scroll up/down the main menu with Home and Menu buttons, menu disappears and appears again, resulting in 2 button presses to scroll up/down once.

2. When I go to "Install from .zip file" and scroll thru the menu 3 times (3 cycles), a menu called "Back button on menu" or something like that activates. Not sure if this was meant to take so many cycles to be triggered.
[HD2 Android NAND Development] olafec:
The attached for NAND?

Sorry, but in the first post there isn't the Recovery for NAND installation...where I find it?
[HD2 Android NAND Development] seadersn:
it's in the attachments, flashable zip file: http://xdaforums.com/attachment.php?attachmentid=769717&d=1320272209
[HD2 Android NAND Development] krook6023:
Oh... It's there! If you are unsure how to install this there are a few hundred guides that you can read.
[HD2 Android NAND Development] CheongKing:
Can anyone help me..

I'm trying to upgrade my recovery from v3.0.2.4 to v5.0.2.6.

I tried overwriting the image file of the old version and run the DAF.

I got the following error.

An error has occurred

Read below for more information

Error Description: Config load failed.

Info: .\RSPL\RSPL.cpp (725)

Error Description: CONFIG: file not exist

Info: .\RSPL\RSPL.cpp (359)

So how do I about in upgrading the software..

Can anyone help?

Thanks in advance
[HD2 Android NAND Development] casemandan:
easy fix

the new recovery image file doesnt match the script file name....

just either rename the file or change the script in flash cfg file so that the image and the blue script below match

or for an even easier way just flash the attachement its all done

and its 5.0.2.7

and just open up the flash.cfg and adjust the values in red to your need for the rom you want to flash

misc ya 1M

recovery rrecov|ro|nospr filesize recovery_5.0.2.7-20111121_leo.img

boot yboot|ro 8M

system ya 200M

cache ya 11M

userdata ya|asize|hr allsize
[HD2 Android NAND Development] googlephone:
You need to enter magldr flash mode before you run daf.exe.
[HD2 Android NAND Development] CheongKing:
Yo casemandan, Thanks! Its Fixed!!! :):)
[HD2 Android NAND Development] 4D3:
what do you mean...in the file downloaded on this post there are no zimage and initrd included.

What Mistake?

so you are supposed to use ad recovery not AD SD?

---Note, how hard is it to get some complete instructions? (and working files?)

MG
[HD2 Android NAND Development] 4D3:
I have task 29 using deloops exe and ran your spftware...DOESNT WORK

I have task 29 using MTTY and ran your software...DOESNT WORK

I have flashed a WM rom, ran MAGLDR from there and ran your software...DOESNT WORK

how many times do i have to try and get this failing?

MG
[HD2 Android NAND Development] af974:
Yes my friend, you need to use ad recovery with all new cwr and those informations were write in RaiderX original cwm thread, since this is an update to that , it was supposed that users should know how to boot into it.
[HD2 Android NAND Development] seadersn:
i'll post the ad sd files in roundabout half an hour.

mystic what exactly are you using...??? magldr and ad recovery menu point or magldr and ad sd...?

if ad sd (a relict of sdcard times and < magldr 1.13), choose (in magldr 1.13, nothing else) ad recovery, which boots from nand. maybe the old sdfiles are on your sdcard and you are using them...

anyeay, i'll post the files needed for starting recovery from sdcard in roundabout half an hour. copy these to your sdcard root and you're done, i believe.
[HD2 Android NAND Development] seadersn:
k, the sdcard files are online and first post is updated.
[HD2 Android NAND Development] seadersn:
genius, extract the sd files to your sdcard and report pls, if the problem is still present for you :)

and: i've pm'ed him the files for testing before making non working sth public and posting them.

it's the new feature of magldr 1.13 to boot recovery from nand, so i assumed this needs no extra statement :)
[HD2 Android NAND Development] 4D3:
Hi,

The SD files worked!! i dont understand what the problem was!!

do you think that because i had not removed the sd files from 3.0.0.5 from my sd card it could have been booting that?

MG
[HD2 Android NAND Development] seadersn:
jep, it must have been. i don't have another possibility in mind :)

do you believe now that it works? :D
[HD2 Android NAND Development] stirkac:
guys, seriously, ditching magldr for clk will be one of best Android+HD2 decisions. why? it works perfecly as fastboot/recovery/adb is used natively on android devices, you don't get effin 123456 GO GO GO every time(simply childish) instead nice stock htc logo same as spl has. daf roms are rare nowdays(they would need converting), everyone has cwm zip packages.
[HD2 Android NAND Development] clyder:
Just did a 3.0.1.4. install, updated my build and restored old data and all went through without any problem.
[HD2 Android NAND Development] seadersn:
good to read :) thx for feedback ;)
[HD2 Android NAND Development] OCedHrt:
Know if charging when off is included in 3.0.0.14?

http://xdaforums.com/showpost.php?p=11649322&postcount=170

Not working with Tytung-r7.
[HD2 Android NAND Development] seadersn:
are you using CLK or magldr? from where did you get tytungs r7?
[HD2 Android NAND Development] seadersn:
anyway, it's included in cwm and working with cLK / tytung > r6; and tytung has updated his git with the fixes, they get compiled in automatically if one is compiling it from his sources.
[HD2 Android NAND Development] tytung:
I have released it in my post.

http://xdaforums.com/showpost.php?p=10429937&postcount=3
[HD2 Android NAND Development] seadersn:
yep, i know :) but i thought, somebody released a cLK version or sth. in another thread.
[HD2 Android NAND Development] pongster:
posted my initrd.gz for CLK on cedesmith's thread... you can try that out if it will fix your market download/cache stuff... :)
[HD2 Android NAND Development] langthang:
I've install successful it without error.

Thanks for all
[HD2 Android NAND Development] mattfmartin:
Cool thanks Pong, will check it out when I get home from work.

On a side note, does anybody know why the clearing the dalvik-cache always hangs about 90% of the time when its in the process of going to the second screen asking to be cleared. I've had this problem since the very first recovery on magldr.

Sent from my HTC HD2
[HD2 Android NAND Development] seadersn:
the userdata partition has to be mounted first; this causes this sometimes :( if you mount sys / data partitions manually, this also appears sometimes.
[HD2 Android NAND Development] jairrab:
For some reason Rom Manager app support for CWM on clk stopped working for me. If I try to do a backup within rom manager it simply boots me into cwm recovery. Im using dorimanx 3.0.2 rom. Anybody here experienced same problem?
[HD2 Android NAND Development] mdskrzypczyk:
That's how the app works... when you hit install zip or backup, it reboots into recovery to perform those actions because all the partitions that are modified by those operations are mounted while the phone is on.
[HD2 Android NAND Development] jairrab:
Sorry for not being clear. The problem is that while it does boot into recovery, it doesn't perform any of the actions it was intended to do (i.e. backups or flashing a new rom). It just reboots into recovery. Thanks.
[HD2 Android NAND Development] realmadrid_cf:
Please add options:

And Console command.

See source: http://xdaforums.com/showpost.php?p=4259325&postcount=1

and sample Recovery: http://xdaforums.com/showthread.php?t=566669

Thanks
[HD2 Android NAND Development] mdskrzypczyk:
Oh I see what you're saying. Does it work if you boot into recovery manually and do these procedures?
[HD2 Android NAND Development] jairrab:
Yes it can do the procedures if I do it manually in recovery.
[HD2 Android NAND Development] arif-ali:
Its nothing wrong with recovery.

Your rom doesn't mount cache correctly and therefore not able to send the correct commands

Can you send the result of

* mount

* df

* ls -l /

* ls -l /cache

* ls -l /cache/recovery
[HD2 Android NAND Development] jairrab:
Here's what I got for /cache & /cache/recovery. Hope this post well, I'm using tapatalk to post terminal output.

# ls -l /cache

total 20

drwxrwxrwx 2 1000 1000 16384 Dec 26 16:32 dalvik-cache

drwxrwxrwx 2 root 0 40 Dec 26 17:00 download

drwxrwxrwx 1 root 0 2048 Dec 24 10:05 lost+found

drwxrwxrwx 1 1000 2001 2048 Dec 26 15:18 recovery

# ls -l /cache/recovery

total 5

-rwxrwxrwx 1 root 0 4292 Dec 26 15:17 last_log

Edit : included screenshot of terminal output :
[HD2 Android NAND Development] arif-ali:
I can't gather anything from that, please give the output of all the commands I mentioned.
[HD2 Android NAND Development] arif-ali:
The cache partition is not mounted correctly, basically from the cache mtd block the recovery folder needs to be in /cache/recovery. There is something in the ROM you are using that is not getting it done correctly or a post app that you have installed that is not doing the correct thing

So you have the mtd5, i.e. bind mount of it into /cache, then what you need is the following script

mkdir /mnt/cache
mount /dev/block/mtdblock4 /mnt/cache
mkdir /mnt/cache/recovery
rm -f /cache/recovery
cd /cache
ln -s /mnt/cache/recovery recovery

Once this is run, then try again.