yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Krendelrus:
Is it only for cLK? or for MAGLDR too?

great job, thanks
[HD2 Android NAND Development] arif-ali:
It's for both,

Will upload cwr update and SD build soon
[HD2 Android NAND Development] arif-ali:
I have updated the post with the attachments for CWR and SD

See post here

enjoy !!! :D
[HD2 Android NAND Development] Drew99:
There are absent 150Mb layouts in cLK_1.4.0.1_layouts_arif.zip
[HD2 Android NAND Development] arif-ali:
Thanks for pointing that out, there was a typo in one of my scripts in generating the layouts.

I have updated the attachment in the post
[HD2 Android NAND Development] davidwxh:
Hi Arif-ali!

Any different between #431 and #489's attached zip file? Which file is CWR3.0.2.8?:eek::eek:

Thanks for you great job!

Sorry for may bad english.
[HD2 Android NAND Development] arif-ali:
A few cosmetic changes, so that it no longer says it is for clk or magldr, as it works for both.

And updated to the latest codebase from git, which ha a minor change, which identifies which partition is being formatting at the top of the screen; which doesn't really affect the implementation of CWR, but useful, to be there for double-checking purposes.

But in-terms of implementation, it is exactly the same.
[HD2 Android NAND Development] diesburg:
Are you not updating OP until there is an "official" update release? (if thats what you call it?)
[HD2 Android NAND Development] arif-ali:
I can't update OP, so wait for seadersn to get back for that. I think he is on a break at the moment. In the meantime I will update in this thread
[HD2 Android NAND Development] seadersn:
jep, i can and will do this today; after my new bike frameset arrived :D

break is correct, jup; at least regarding this special thingy here :)
[HD2 Android NAND Development] diesburg:
Awesome, couple questions.... is this new cLK version and recovery version stable without bugs/problems? And will I be able to restore from backups made with 3.0.2.5 recovery? Thanks for the help and thanks for the quick responses.... also thanks for the assload of layouts you supplied for cLK.....oh yra, should I ignore any recovery updates in Rom Manager?

Also, would it be possible to put in a confirm yes/no option before backup? So after you choose backup option, a yes/no screen is next before the backup job continues....I ask because several times when wanting to restore from a backup, I accidentally hit backup instead of restore..... and of course had to wait for the backup to finish for me to do the restore I originally intended to do.....
[HD2 Android NAND Development] arif-ali:
The cLK seems to be looking good, I haven't had any complaints/issues that anybody has reported. I have been using the same cLK and recovery since I released it, and all seems to work well.

The next RM update will have the same CWR changes that I have made here, so, you will be able to use that as well.

We will see wrt to the yes/no for backup that should be pretty easy to set-up, but I am putting priority on getting a CWR that will work with any ROM now that the same CWR works for both magldr. RaiderX has made his CWR work such that cLK ROMs work with magldr, but not sure how he has done that. I will be taking one step more, and doing it such that a magldr rom woking in cLK amd clk rom working in magldr, so that ROM chefs, only need to provide one type of ROM. If RaiderX can contribute to what he did, then that would great, otherwise I will spend some time looking at the code, and implement this feature.

The new cLK allows ROM chefs to look out for /proc/cmdline to see if they are running under clk or not, and make modifications to files as appropriate dynamically in their ROMs, again this allows for only one ROM release for both bootloaders. This way ROM chefs need to do less work, and less files to upload
[HD2 Android NAND Development] diesburg:
Awesome, of course put other things like that first. And if it's going to cause problems with other things or be a pain in the ass to put that in, just forget it because it's just a small thing and if it can't be put in, I'll just be slower/more careful when going about the menus to do restores....lol... I just thought it would be a good suggestion to put it in, in the future if possible. As always, thanks for the helpa nd replies... you and seadersn have been a HUGE help to me when I've needed help with cLK and CWM....if it weren't for you 2, I probably wouldn't be using cLK right now...lol... so thanks, A LOT!
[HD2 Android NAND Development] diesburg:
I have a strange issue.... not sure if it's something to do with CWM.... but here it is... I made a backup of my whole setup in CWM of nexushd2.GB.... when I restore from the backup, I immediately get gapps force close error on first boot..... so I am not signed into any google account and I cant sign into one because google is not listed under add accounts in the accounts menu under settings.......but if I take that exact same system.img that I restored with CWM and flash it with fastboot instead.... when I boot up there is no gapps force close and when i go into market, I'm prompted to sign into google and everything is fine.....any ideas whats going on here? It's weird it did this at all because when I made the backup which I have tried remaking several times with same results.... I was signed into a google account.....

EDIT: I said screw it, I'm starting from a clean install and doing it all over again.... I am baffled as to why my google account sign in got all fubar'd after backing up though.....

EDIT: Corrupted SDCARD.... formatted card and restore from the same backup worked just fine....lol
[HD2 Android NAND Development] clyder:
higher battery drain while in CWR?

Hi,

my phone was left for about 5 hours in clockworkmode last night. Battery before I started was about 65%... then I fell asleep while CWR was doing a backup. This morning I continued and soon the phone just turned off, and later I couldn't get it to start without turning off after half a second.... Finally I managed to make it stay on, booted into android just to see that battery was at 1%. Is it a known thing for very high battery drain while inside CWR? I never stayed in it very long before this so never noticed anything.
[HD2 Android NAND Development] :
...mhh, i dont tkink that cwm is responsable for the drainage, more the screen that doesnt goes to standby (;
[HD2 Android NAND Development] clyder:
Yeah, I guess... I was kind of still in panic mode while I was writing my earlier post :)
[HD2 Android NAND Development] arif-ali:
CWR 3.1.0.1

Hi all,

I have just seen that my nightly builds have built a new version of CWR

If people want to test, then that would be great

recovery_3.1.0.0-1305511372_leo.img

recovery_3.1.0.1-1305597724_leo.img

I will test this more tonight, and will do an official release for this thread then; obviously with changelogs.
[HD2 Android NAND Development] clyder:
I've tried recovery_3.1.0.1-1305597724_leo.img and found nothing wrong with it so far.

What I tested was:

-installed image through terminal emulator

-in CWR did a backup, wipe cache, dalvik cache, mount USB, clicked on report error just to try the option :), installed few roms and updates, then did a recovery of previous backup, clicked on reboot now and now I am back in android....

If I see anything wrong I will report it here....
[HD2 Android NAND Development] Drew99:
What difference between these files?
[HD2 Android NAND Development] arif-ali:
Sorry for the confusion, all the previous versions never stepped between 2 days

the first was a nightly from yesterday, and the second was from today

So bound to have differences

changelog and details on main release with CWR and SD links to come soon

Changelog: (taken from git)

* bml_over_mtd: Take care of bad blocks on "boot" partition for Samsung Galaxy S Phones.
* Try to mount vol->device2 partition to UMS.
* recovery: display mount point when confirming format
* Use TARGET_RECOVERY_PRE_COMMAND before calling __reboot() recovery
* Allow per device unsafe-to-format partition list
* Do not close the zip archive prematurely. It may be accessed later for a firmware update.
* set the env for UPDATE_PACKAGE (the source zip) for update-binary. This allows shell scripts to use the source zip.
* also set UPDATE_PACKAGE in updater for old recoveries

btw, thanks clyder for testing that much, much appreciated
[HD2 Android NAND Development] arif-ali:
CWR 3.1.0.1

OK, the new files have been attached

The Changelog is below: (If you can understand it, otherwise check git from OP)

bml_over_mtd: Take care of bad blocks on "boot" partition for Samsung Galaxy S Phones.

Try to mount vol->device2 partition to UMS.

recovery: display mount point when confirming format

Use TARGET_RECOVERY_PRE_COMMAND before calling __reboot() recovery

Allow per device unsafe-to-format partition list

Do not close the zip archive prematurely. It may be accessed later for a firmware update.

set the env for UPDATE_PACKAGE (the source zip) for update-binary. This allows shell scripts to use the source zip.

also set UPDATE_PACKAGE in updater for old recoveries
[HD2 Android NAND Development] :
Hi,

where have I to put this command in?

Is it possible to use another way to install??

thanks
[HD2 Android NAND Development] mattfmartin:
Hey arif, is the cwr file below for clk and magldr?
[HD2 Android NAND Development] nic.stl:
For both
[HD2 Android NAND Development] mattfmartin:
Thanks nic-stl. Keep up the good job Arif, you've been

doing one hell of a job:p
[HD2 Android NAND Development] brainmaster:
One question about the CWM zip - when I flash that through the CWM is my partition layout gonna stay the same?

If I want to flash the CWM file and to change the partition layout how can I do that?
[HD2 Android NAND Development] arif-ali:
Partition layout will stay the same

For the second point, use the same method that was used with RaiderX303's thread. download that, replace the recovery-raw.img with the one provided, and modify the flash.cfg. My recommendation is not to use filesize for the recovery, but in-fact use 5M, that way if there is any changes to recovery, you don't have to worry about reflashing the whole ROM again.

for both

terminal emulator on the phone, it's in that same howto if you read it,

it says

"and run following in terminal emulator"
[HD2 Android NAND Development] arif-ali:
if you are using cLK, then you need to use my modified cLK, that was posted about a week back in this thread and the cLK thread; in order to use this CWR

but yes, it is for both cLK and magldr
[HD2 Android NAND Development] kaiserlein:
weird, I didn't flash the modified CLK yet but CWR 3.1.0.1 seems to work anyway??? I just made a backup with it.
[HD2 Android NAND Development] arif-ali:
yes, it will work to an extent, but there will be issues with restoring at some point. we had issues, that is why we had separate CWRs previously. if you don't have problems when you do further things with it, then good luck
[HD2 Android NAND Development] kaiserlein:
I'm not going to take any risk, I flashed the modified CLK now :D
[HD2 Android NAND Development] seadersn:
today i've got the time for updating first post with arif's new achievements and recoveries; it's time, isn't it...? :)
[HD2 Android NAND Development] mirroalex:
i don't get it, how can i update my CWM without screwing up everything (partition layout , rom) ? currently i have CWM v3.1.0.0 ...
[HD2 Android NAND Development] arif-ali:
Check OP, you can use flash_image script to do that
[HD2 Android NAND Development] mirroalex:
can you explain it step by step?
[HD2 Android NAND Development] fuuunkdat:
Arif, Do i still use the same command line as the one in the OP in the emulator with your img update zip? I noticed that it was named different from the one in the OP and wondered if this made any difference for the command line? Any help Greatly appreciated.
[HD2 Android NAND Development] zach.antre:
1. Copy recovery image file to SDcard

2. Run Terminal emulator

3. Type command: su

4. Type command: flash_image recovery /sdcard/image_filename.img
[HD2 Android NAND Development] fuuunkdat:
I keep getting an error when trying to update to the 3.0.2.5.img in the emulator. It runs and say's : mtd successfully wrote block upto 380000. Then i get error -1. error writing recovery? Can anyone help me with this error Please.
[HD2 Android NAND Development] arif-ali:
how big is your recovery partition in the emulator? it needs to be at least 5M
[HD2 Android NAND Development] fuuunkdat:
Thanks for the reply Arif-Ali. But I flashed it using daf in the end. Because whatever I did with the emulator caused my phone to bootloop. I used terminal emulator from the market. Couldn't see any option to check or change the recovery in it. I use standard cwm 150 recovery file. Shouldn't play with what I don't understand is the moral of the story ;o) I did cwm backup before hand though so no harm done. Would like to try and understand where I went wrong though? Thanks again Arif-Ali.
[HD2 Android NAND Development] seadersn:
k, updated first post and title with arif's nice work :)
[HD2 Android NAND Development] arif-ali:
Thanks for updating, now less confusion for people I hope :)
[HD2 Android NAND Development] arif-ali:
first of all, why are you flashing a magldr rom in cLK, that on it's own will not work. You need to do something further to get it work.

cLK 1.4.0.1 works, as many people have downloaded without any problems, an myself, I have been using this as well.

can you retry with a cLK rom, and let me know what you get.

Plus, please don't double post, thx
[HD2 Android NAND Development] chshrm:
thanks for your quick reply, i like the CLK flash mode, therefore, i just want to make this tool can work for both clk rom and magldr rom. ok, i will try to test this issue for a clk rom, any problem i will post it here. thanks again!
[HD2 Android NAND Development] arif-ali:
Which tool are you talking about? I don't understand

what do you mean by CLK flash mode?

CWR works for both cLK and MAGLDR

please explain
[HD2 Android NAND Development] 10507:
Does the new recovery only work with cLK 1.4.0.1? I flashed recovery with older cLK, but when I check in RM, I still have recovery 3.1.0.0 instead of the new 3.1.0.1.
[HD2 Android NAND Development] chshrm:
1.flash Task 29 with Radio 2.15.50.14

2.flash clk 1.4.0.1

3.flash cLK_Rcovery (fastboot recovery_leo.img CWR files)

4.flash ROM file（Magldr zip）

5.flash Kernel files initrd.gz and zImage（take them from Zip Rom）

in the above procedure, i use CWR files, ok, the rom can successfully loading and use normally, but only one problem, i can not go to the internet. and the weather cannot be refresh.

btw, i use the rom " Kingdom_Sprint_WWE_0.81.651.0_v3.7.zip" for the test.
[HD2 Android NAND Development] arif-ali:
Yes, that's right

Don't worry what RM says, flashing CWR using this method does not update RM, to tell it that you have a new version. Don't worry, you do still have 3.1.0.1.

maybe for something to think about for me to implement in the future
[HD2 Android NAND Development] louie317:
1. flash Task 29 with Radio 2.15.50.14

2. flash bootloader - cLK or MagLdr

3. flash recovery - cLK recovery for cLK bootloader or MagLdr recovery for MagLdr bootloader. Do NOT MIX.

4. flash ROM - cLK ROM for cLK or MagLdr ROM for MagLdr. DO NOT MIX.
[HD2 Android NAND Development] arif-ali:
I am not sure if this rom has cLK support or not, but your idea was good. There are a few things you need to convert a rom to cLK, and I have already mentioned these in the cLK thread

1. comment out the msm_rmnet.ko line from /system/etc/init.d/01modules

2. use 0.6 wrapper from letama

3. grab the relevant ppp files from one of the zips from the cLK thread, i.e. stuff in /system/etc/ppp,

4. Touch the /system/ppp file

Once you do all these, then all should work

FYI,

1. you can mix recovery, with the latest once CWR

2. you can install a magldr rom with cLK, as long you know what you are doing afterwards. that is what we are doing in the CM nightlies thread
[HD2 Android NAND Development] arif-ali:
CWR 3.2.0.0

Hi Folks,

here is an update

enjoy!!

The changelog on github doesn't really make much sense, see commits, for more details

See OP for more details on flashing
[HD2 Android NAND Development] seadersn:
update first post: done :)
[HD2 Android NAND Development] EhdisChris:
Which zip to use if upgrading using "DAF"?

Also, Will flashing the 3.2.0.0 Zip file via CWM erase the nand custom rom partition?
[HD2 Android NAND Development] seadersn:
you can use any but not the sd zip, of course; and nope, custom partition layout isn't touched, because clockworkmod has nothing to do with partitioning etc; it only was flashed together with a partition layout. cwm is "independent" from p.layouts :)
[HD2 Android NAND Development] dude0316:
I have been trying each new update and every time I restored a Rom when it booted up all I got was fc after fc I had to always load cwr 2.5.0.7 then restore same file and all was good. Now finally cwr 3.2 has fixed this !!!!!!!

Thanks to all involved in this project for all your hard work.
[HD2 Android NAND Development] EhdisChris:
Flashing the CWR Update Zip via CWM doesn't work.

*(Update 7) and the img file is not present?
[HD2 Android NAND Development] elmng:
i agree with you. i got some weird cannot partion or something when i tired and then it aborted
[HD2 Android NAND Development] htcfreak:
Works great for me, thank you..!!! :D
[HD2 Android NAND Development] Lozone:
CWR zip works for me also.
[HD2 Android NAND Development] daeshawn:
I notice it doesnt load sometimes after go go go. Have to pull battery. Not all the time but at least half
[HD2 Android NAND Development] mystery4869:
need to customize partition size on updating cwm like a fresh install? how to do tat?
[HD2 Android NAND Development] antonmandara:
Happened to mine since upgraded to 3.1.0.1 (yes, sometimes)

Not upgraded to 3.2.0.0, yet....
[HD2 Android NAND Development] chshrm:
Thank so much, with your help, and the cLK.zip Fixes, I finally successfully flash Magldr rom with CLK tools, and everything now work normally. hopefully more progress in this tools.
[HD2 Android NAND Development] elmng:
i fixed it first i installed http://xdaforums.com/showthread.php?t=1090783. the mag version. and in recovery it said 3.1.01 then i came back to this thread and installed the cwr version and everything worked out fine. thanks you guys for making my hd2 awesome.
[HD2 Android NAND Development] maddoc1007:
recovery 3.2.00 leo.cwr zip wont install

i keep getting this message when trying to install 3.2.0.0. leo.cwr zip using 8 ad recovery the messae is error in sd/recovery_3.2.0.0_leo_CWR.zip (Status 7) installation aborted i have clockwork recovery v3.0.0.5 already and raphigna 4.2 in nand on hd2 why wont it allow me to install zip is there problem with it wiped dalvik cache etc still wont allow me to install any help please?????:(:( ps: now clockwork wont work on phone at all get message ERROR ERROR invalid boot image header
[HD2 Android NAND Development] EhdisChris:
Flashing the the CWR zip won't work unless you have 3.0.2.5 and up i believe.

You need to reinstall a earlier version of CWM via CWM DAF.

I just had all this happen to me yesterday.
[HD2 Android NAND Development] maddoc1007:
why wasnt this said in first page of thread am a noob will doing this wipe my rom and data ???? thanks for quick reply. iv read up on cwm and in order to install u have to start all over again is ther anyway to repair magdlr 1.13 ad recovery without having to reinstall everything partition layout etc and rom??? if so could you provide link to thread thanks
[HD2 Android NAND Development] seadersn:
compare filesize of 3.0.0.5 and 3.2.0.0 ;) as already said, the partition size for the recovery partition given in flash.cfg was 'filesize', means that size of partition is the same as the filesize of the 3.0.0.5 img. now the recovery is bigger because of other kernel used, new features, additions etc. this in turn means, that the new recovery doesn't fit into the old partition -> partition is too small -> error.

you see the problem? you can do a backup in android itself, with titanium backup for example, and reinstall the partitions / clockworkmod, and afterwards restore the apps etc.

this was written about two or three times in this thread :) it's sh*t, that the new recoveries are bigger in filesize, yes. but there is progress on everything, and everything changes, so also the filesize / needed partition sizes...
[HD2 Android NAND Development] seadersn:
or use the sd version of cwm for backing up your current rom ;)
[HD2 Android NAND Development] maddoc1007:
if this is the case then why dont developers deliberatly make the partition larger to allow or future expansion???:(:( i still think there should be a patch made by some developer to repair ad recovery instead having to reinstall 400mb partition for rom im using and reinstalling rom i have all my apps backed up regularly with titanium.....

For both via CWR:

•Download the recovery_3.2.0.0_leo_CWR.zip file onto sdcard

•Go into recovery by either holding home key in cLK or using the 8. AD to recovery in MAGLDR

•Select Install zip from sdcard

•Select Choose zip from sdcard

•Navigate/Select the recovery from the sdcard

•Select yes to install the recovery

reboot into recovery, and hooray, you are in the new recovery

this should be added:- any noob updating to 3.2.0.0 must have clockwork 3.0.2.5 or above or ad recovery will stop working in magldr 1.13
[HD2 Android NAND Development] aaznak:
hello,

recovery_3.2.0.0-flash -> ok

but space and 265 MB ram for what?

Thank you

HD2 TyphooN_v3.3.3-MAGLDR
[HD2 Android NAND Development] tdizzle404:
so what do I have to do to get CWM 3.2.0.0 on my HD2? I need a 150 par why cant i just using MGLDR?
[HD2 Android NAND Development] tdizzle404:
I just refered to this and got 3.2.0.0 Thanks man it worked.
[HD2 Android NAND Development] seadersn:
updated second post with info and new cLK 1.4.0.1 layouts :)
[HD2 Android NAND Development] Kameirus:
could some one please make a couple new sizes for me

a 425/5 nbh and 425/44 nbh

and a 450/5 nbh and 450/44 nbh

for clk please ..i dont really like the new installer that was made

but am using the older installer that is much easier to use

Thanks in Advance
[HD2 Android NAND Development] casemandan:
you can only do 445mb max
[HD2 Android NAND Development] arif-ali:
OK, these will be done, soon, and will upload with a new set with new values above 400

This should have gone in the cLK thread, but no matter, will be up in about 30 mins or so
[HD2 Android NAND Development] arif-ali:
with a tmous, you could do bigger, so these will be mostly for those who have a tmous, i.e. leo1024
[HD2 Android NAND Development] Kameirus:
Thanks Arif ..some of the newer sense builds are needing bigger partitions

sorry didnt know which thread to pot it in
[HD2 Android NAND Development] arif-ali:
new Layouts upto 450

Uploaded new layouts

80 to 450, with gaps of 10, all with option of 5M and 44M cache

I hope that helps
[HD2 Android NAND Development] seadersn:
3.2.0.1 is out, i will attach it here and @ first post in ~ an hour.

find it attached :)
[HD2 Android NAND Development] seadersn:
updated; have fun.
[HD2 Android NAND Development] lippa:
CWR gives me an error and wont flash. Will try and re-download again and report. Anyone else can report please?

Thanks
[HD2 Android NAND Development] seadersn:
gave me an error too; my mistake @ rezipping :( sry ;) now it's working.
[HD2 Android NAND Development] :
Can you give an option in the "Partition SD Card" Option for a 0M ext size? Otherwise, the recovery is working great!

Thanks in advance!
[HD2 Android NAND Development] seadersn:
you mean for pure formatting of the sdcard, w/o any extra partitions? this is possible already:

- go to "mounts and storage"

- choose "format /sdcard"

altering / changing / editing the partition menu makes no sense in my opinion, because it does, what the name is saying: partitioning, not formatting. of course, formatting is included in this process, but main point of this menu is the partition thing for sd-ext. :)