[23 Nov 12] cLK

Search This thread
P

prime_225

Guest
Working on something but it's a bit problematic right now, should have something awesome next month ;)
Ok, good to know.

---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------

Why does it need regular updates? It's still more recent than magldr :p also the last release was on 22/2/12

Sent from my HTC HD2 using XDA
I am talking about rick's lk, not kokota's lk. You should have seen that.
 

Burag

Senior Member
Jun 29, 2009
295
102
Working on something but it's a bit problematic right now, should have something awesome next month ;)
I bet it's somehow related to .38 kernel... :p

BTW. Rick, do you have any plans for cLK 1.5 release? How about releasing kokotas' version as 1.5? It's the most advanced and still rock solid build of cLK.
 
P

prime_225

Guest
I bet it's somehow related to .38 kernel... :p

BTW. Rick, do you have any plans for cLK 1.5 release? How about releasing kokotas' version as 1.5? It's the most advanced and still rock solid build of cLK.
If that's the case, then it would mean a breakthrough for our hd2.
 

Hammerfest

Senior Member
Apr 3, 2008
1,682
286
San Antonio, TX
well since Dorimanx is giving up the ghost so to speak on his HD2, figured id give my HD2 one last full wipe/update...

Whats the recommended cLK? OP's or Kokota's?

Or, as Rick posted about having a release this month, do you think it will be in the 1st half or 2nd half of the month? If its the first half i can wait the 15~ days before I do the scrub down...
 

Screemi

Senior Member
Sep 27, 2010
244
26
i am using 1.5-rc1. it is working just as it should. as cwm i usingn which can be found he touch recovery beta 8.

i am just waiting for the release of ricks stuff and hoping cotulla will release the stuff he is working on for ages :)
 

Hammerfest

Senior Member
Apr 3, 2008
1,682
286
San Antonio, TX
""" if you don't see the option to 'PRINT BAD BLOCK TABLE' under 'SETTINGS' then your device doesn't have bad blocks."""

I am so confused... how the hell can me, someone who does Task29 before nearly every ROM flash not have a single bad block... (i havent flashed in a month or 2, but before I was flashing nearly nightly for the Dorimanx ROM/Kernel release's and prior to that Ty's ROM with Dori's mod pack)...

My HD2 must be GODLIKE!... jkjk...

ANYWAY, Since I didnt see it discussed much, I guess enabling the ExtROM 24MB gets partitioned as cache, as the recommended is there any issues with changing that? (ive read people's issues, I just wanted to know if EVERYONE had the issues, or just some?) Id like to try at least because I like having just 2MB Cache (with market fix)

Also, whats the recommended partition layout/order? For best performance preferable (hell I cant even think of how that would be test-able...)


(cLK 1.5.0.3 from kota's 2-22 release)
 

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
""" if you don't see the option to 'PRINT BAD BLOCK TABLE' under 'SETTINGS' then your device doesn't have bad blocks."""

I am so confused... how the hell can me, someone who does Task29 before nearly every ROM flash not have a single bad block...
I suppose that your device has the Samsung Nand chipset(T-Mobile HD2?).
So doing Task29 before each flashing probably saved your device from having bad blocks.
Important information concerning Leo flashing algorithm:

Leo is manufactured with 2 different NAND-Flash ROM chipset types. You can detect the type entering tri-color boot mode.
If you see
PB81120 SS-B3 in the first line - that means NAND-Flash ROM from Samsung - KBY00U00VM
If you have
PB1120 HX-B3 in the first line - that means NAND-Flash ROM from Hynix - h8BFS0WU0MCR

After one year usage Samsung chipset usually has a dozen of bad clusters. Hynix normally has none of them or just a couple.

So for devices with SS-B3 and Samsung chipset recommended flashing algorithm is the following:
1. Task29
2. Task32

For devices with HX-B(3/С) and Hynix chipset - Task28 is totally acceptable.
ANYWAY, Since I didnt see it discussed much, I guess enabling the ExtROM 24MB gets partitioned as cache
Yes, that's how it is working, but you can change that as much as you want: "Id like to try at least because I like having just 2MB Cache".
(ive read people's issues, I just wanted to know if EVERYONE had the issues, or just some?)
According to Cotulla's post, as far as I understand, I'd say EVERYONE will eventually face some issues if last 24MB are used for anything else than cache.
Also, whats the recommended partition layout/order? For best performance preferable (hell I cant even think of how that would be test-able...)
I can't either see how the partition layout would affect the performance in general, but in case of a device having bad blocks it could. Because you could make the layout in such way that the bad blocks would not affect your system.

Regards!
 
  • Like
Reactions: __ and Burag

Hammerfest

Senior Member
Apr 3, 2008
1,682
286
San Antonio, TX
I suppose that your device has the Samsung Nand chipset(T-Mobile HD2?).
So doing Task29 before each flashing probably saved your device from having bad blocks.


Yes, that's how it is working, but you can change that as much as you want: "Id like to try at least because I like having just 2MB Cache".

According to Cotulla's post, as far as I understand, I'd say EVERYONE will eventually face some issues if last 24MB are used for anything else than cache.

I can't either see how the partition layout would affect the performance in general, but in case of a device having bad blocks it could. Because you could make the layout in such way that the bad blocks would not affect your system.

Regards!

Interesting, but no, I dont have the Samsung mem chips, its a T-Mobile USA HD2 but its using the Hynix mem chips...

While im on that, thanks for listing that info about wiping, sadly, the only "Task" tool I remember seeing was long ago (it looked like the task29 tool but had the options for many other "task" tasks... pun intended), else, I wouldnt know how to do anything besides Task29 :p (also of note, windows junkie :D )

Im confused as to why issues would occur if it wasnt cache and wouldnt if it was cache... it still gets used, was there a more detailed explanation (i read the post but couldnt make heads/tails of it), either way, boggles the mind still


Yeah, I could guess, im just a tweak junkie so if changing the order of partitions around would speed up boot it would have interested me (like multi partitioned HDD's, mostly in the past, but even still today sometimes)


AND finally, thanks for the reply, very interesting!
 

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
Im confused as to why issues would occur if it wasnt cache and wouldnt if it was cache... it still gets used
Well my answer was not really accurate:)
I haven't tried many roms, but I believe most of them have moved all the cache stuff to data/sd-ext,
so cache partition is not really used for anything other than recovery purposes.
So correct me if I'm wrong but whatever may happen to that partition wouldn't affect the whole system operation.

Regards!
 
  • Like
Reactions: __

Rick_1995

Inactive Recognized Developer
Sep 3, 2009
1,118
3,017
Santa Clara
Well my answer was not really accurate:)
I haven't tried many roms, but I believe most of them have moved all the cache stuff to data/sd-ext,
so cache partition is not really used for anything other than recovery purposes.
So correct me if I'm wrong but whatever may happen to that partition wouldn't affect the whole system operation.

Regards!
/cache is symlinked to /data/cache
It is used for market downloads, system upgrades through stock android API and recovery. Recovery actually doesn't depend on cache partition (just stores the logs there) but is highly dependent on the misc partition where bootloader, recovery and android write plain text stuff to communicate with each other during reboots, updates, etc.. Usually the commands should be saved as plain text in the first block with offset 0x0.

I need some info about wince romhdr, This is what i have as of now after looking at romhdr in leo's spl, will further look into nk and magldr
Code:
// MSDN article about romhdr
typedef struct ROMHDR {
  ULONG dllfirst;
  ULONG dlllast;
  ULONG physfirst;
  ULONG physlast;
  ULONG nummods;
  ULONG ulRAMStart;
  ULONG ulRAMFree;
  ULONG ulRAMEnd;
  ULONG ulCopyEntries;
  ULONG ulCopyOffset;
  ULONG ulProfileLen;
  ULONG ulProfileOffset;
  ULONG numfiles;
  ULONG ulKernelFlags;
  ULONG ulFSRamPercent;
  ULONG ulDrivglobStart;
  ULONG ulDrivglobLen;
  USHORT usCPUType;
  USHORT usMiscFlags;
  PVOID pExtensions;
  ULONG ulTrackingStart;
  ULONG ulTrackingLen;
} ROMHDR;

header in leo SPL (converted to big endian format)
@ 0x00000040 (file offset)
@ 0x95000040 (Virtual offset)
43 45 43 45 (ECEC signature)
95 07 01 98 (Virtual, inram offset for romhdr)
00 07 01 98 (File offset for romhdr)

@ 0x00070198 (file offset)
@ 0x95070198 (Virtual offset)
romhdr:
dllfirst:
02000000
dlllast:
02000000
physfirst:
95000000
physlast:
95073a0c
nummods:
00000001
ulRAMStart:
97900000
ulRAMFree:
9792a000
ulRAMEnd:
97980000 
ulCopyEntries:
00000001
ulCopyOffset:
9506cfe0
ulProfileLen:
00000000
ulProfileOffset:
00000000
numfiles:
00000000
ulKernelFlags:
00000000
ulFSRamPercent:
80808080
ulDrivglobStart:
00000000
ulDrivglobLen:
00000000
usMiscFlags:
0002
usCPUType:
01c2
pExtensions:
00000000
ulTrackingStart:
00000000
ulTrackingLen:
00000000

what is this ? (right after romhdr in spl file)
00000005
2b81acf7
01cb0238
00074ef8
9506cfd8
9506cf08
9506cf78
95000000
95000000
 
Last edited:
  • Like
Reactions: Burag

ksaleem

Member
Dec 18, 2009
35
6
Please Help

I got cLK 1.5-rc1 installed. I was booting newly updated ROM (IceCreamTosti HD2 ROM) when it failed to boot I pulled the battery out and tried rebooting it but it stops at initial HTC with white background
for some reason it wont go into recovery anymore
I can go into cLK menu but trying to make any change to partition or booting into recovery just freezes the phone.
I have reinstalled cLK 1.5 (using SD card) couple of times with no luck
I have broken charging port

Can you please advice me what can I do.
Is there any way to format my Nand or delete data/cache (considering I can't enter CWM)

Thanks in Advance

Edit: Strange nothing else would work, tried red reset button and now it boot fine. Thanks a lot for great bootloader...
 
Last edited:

Rick_1995

Inactive Recognized Developer
Sep 3, 2009
1,118
3,017
Santa Clara
Can someone test this for me ? no it won't blow your phones/brick them.
It is actually clk 1.4 + using mddi to handle display.

I just want to know if screen/framebuffer comes up.

To return back to magldr/clk1.5, just reflash their nbh and use the same partition config you had earlier using DAF or clk settings. NAND will NOT be touched unless you do it explicitly using fastboot. However taking a backup is encouraged.

*remember to keep the back key pressed while booting.
 

Attachments

  • RUU_signed.zip
    31.2 KB · Views: 23

sathara

Senior Member
Jun 3, 2009
1,189
148
37
the club
Can someone test this for me ? no it won't blow your phones/brick them.
It is actually clk 1.4 + using mddi to handle display.

I just want to know if screen/framebuffer comes up.

To return back to magldr/clk1.5, just reflash their nbh and use the same partition config you had earlier using DAF or clk settings. NAND will NOT be touched unless you do it explicitly using fastboot. However taking a backup is encouraged.

*remember to keep the back key pressed while booting.
flash over clk or this simply flash ..?
 

bojanbl

Senior Member
Feb 5, 2010
633
200
Can someone test this for me ? no it won't blow your phones/brick them.
It is actually clk 1.4 + using mddi to handle display.

I just want to know if screen/framebuffer comes up.

To return back to magldr/clk1.5, just reflash their nbh and use the same partition config you had earlier using DAF or clk settings. NAND will NOT be touched unless you do it explicitly using fastboot. However taking a backup is encouraged.

*remember to keep the back key pressed while booting.

Backing up all of the data and than I will install this ;) I was planing to reflash my phone anyway :)

EDIT: Installed this CLK and I got something like this on display:

cedesmith's LK (CLK) v1.4
[280] ptn 0 name='misc' start=00000219 ...
[370] ptn 1 name='recovery' start=....
.....


Was this helpful?
 
Last edited:
  • Like
Reactions: Rick_1995

Rick_1995

Inactive Recognized Developer
Sep 3, 2009
1,118
3,017
Santa Clara
Backing up all of the data and than I will install this ;) I was planing to reflash my phone anyway :)

EDIT: Installed this CLK and I got something like this on display:

cedesmith's LK (CLK) v1.4
[280] ptn 0 name='misc' start=00000219 ...
[370] ptn 1 name='recovery' start=....
.....


Was this helpful?

Thanks, so mddi works in lk now ;)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 67
    Timeline for experimental builds [Latest version: 1.5.2.1 @ 6/May/2013]

    ALWAYS make a backup before installing any of these test versions and try them at your own risk!

    • Installation:
    • Links:
      1. Compiled binary
      2. Source code
    • Related Projects (WIP):
    • Timeline:
      1. 19/Jan/2012 - FIRST alternative suggestion
        Link
      2. 25/Jan/2012 - UPDATE #1
        Link
      3. 26/Jan/2012 - UPDATE #2
        1. New format option leaves recovery partition untouched. So yeah, no pc needed after formatting !:)
          Basically it erases all the other existing partitions one by one. At the end recovery partition is intact so we can enter recovery interface and flash our preferred rom.
        2. Set userdata as 'auto-size' partition . So default partition table is:
          "recovery:5"
          "misc:1"
          "boot:5"
          "userdata:0"
          "system:150"
          "cache:5"
        3. Revised the 'Enable/Disable ExtROM' option.
          If enabled it will automatically be used for 'cache' partition .
          If disabled 'cache' will automatically return to 5MB size .
      4. 28/Jan/2012 - UPDATE #3
        1. Cleaned some code that was not used .
        2. Added option to convert 'auto-size' partition to 'fixed-size' .
        3. Added option to set a partition as 'auto-size' if one doesn't already exist (just decrease its size to zero).
        4. Small fixes to some features I previously added.
      5. 29/Jan/2012 - UPDATE #4
        1. Revised the 'rearrange partitions' menu.
          We cannot move recovery , cause then we'll have to re-flash it via pc .
          How it works:
          Lets say we have this layout:
          1."recovery"
          2."misc"
          3."boot"
          4."userdata"
          5."system"
          6."cache"
          And we want to change it to:
          1."recovery"
          2."misc"
          3."boot"
          4."cache"
          5."system"
          6."userdata"
          1. Enter 'REARRANGE PARTITIONS'
          2. Select 'userdata' -> Scroll DOWN to 6 -> Select it
            (You should see the change in the order of the partitions immediately! Don't worry nothing is committed. If you exit and re-enter SETTINGS menu everything will be reset.)
          3. Select 'COMMIT CHANGES' -> Select 'APPLY'
          (Of course you still have the option to re-order and re-size the partitions via pc, if the default layout doesn't fit your needs)
          WARNING ! If you change the order of the partitions then have in mind that the same /dev/block/mtdblock<n>, n=0,1,2,... point to different mount points.
        2. Clean up some code
      6. 01/Feb/2012 - UPDATE #5
        1. Added new info when booting
          After the partition table you should see a list with the existing bad blocks IF ANY. (CONFIRMED)
        2. IF there are any bad blocks inside recovery,misc,boot,sboot,cache THEN they will be auto-re-sized by adding 1MB to each one.
        3. Changed some output messages
      7. 02/Feb/2012 - UPDATE #6
        1. Changed the function regarding auto-resizing:
          IF there are any bad blocks inside recovery,misc,boot,sboot,cache THEN 1MB per 1bad block will be added to each partition with bad block(s). (CONFIRMED)
        2. Changed some output messages
        3. Default partition table is:
          "recovery:5"
          "misc:1"
          "boot:5"
          "system:150"
          "userdata:0"
          "cache:5"
      8. 06/Feb/2012 - UPDATE #7
        1. Minor fixes/changes
        2. Changed some output messages
      9. 08/Feb/2012 - UPDATE #8
        1. If you press&hold the middle [MENU] button during (re)booting you can immediately boot android from sdcard(emmc), assuming that you have flashed sboot partition with the appropriate image and you have the required folder in the root of your sdcard.
          Process of having dual boot(without using pc):
          Prerequisite: The folder(usually named 'Android' or 'ics') with the SD version of Android exists in the root of your sdcard
          1. Boot the device in cLK pressing [BACK] button, having the sdcard inserted
          2. Go to MAIN MENU/SETTINGS - Select ADD sBOOT
          3. Select BOOT RECOVERY from MAIN MENU
          4. Select 'install zip from sdcard' and use something like this(this is an example) flash_sboot.zip
          5. Select 'reboot system now' and press&hold [MENU] button to directly boot Android (emmc)
        2. After each change(resize/rearrange parts, add/remove sboot, enable/disable ExtROM) is committed there is no longer the need to reboot. clk will just auto return to main menu, and from there you can select your next action.
      10. 14/Feb/2012 - UPDATE #9
        1. Changed cpu speed to 998MHz.
        2. Added option to show/hide info(ptable and bbtable) at start-up under MAIN MENU/INFO.
        3. If you invert screen colors, the change will remain after rebooting.
        4. The speed of reading/writing or erasing is improved a bit.
        5. Cleaned up some code.
      11. 22/Feb/2012 - UPDATE #10
        1. Removed showing bad block info during startup. Bad blocks can be checked from SETTINGS/PRINT BAD BLOCK TABLE(if any bad blocks exist).
        2. Added chipset info in header.
        3. Cleaned up more unused code.
      12. 13/Apr/2012 - UPDATE #11
        1. Ported Rick's latest commit.
        2. Added ability to triple boot. It works like secondary boot 'sboot'; you can add a tertiary boot partition named 'tboot' and the rest work the same.
        3. Added "USB" mark for usb detection; if your device is connected to the pc via usb you should see 'USB' at the bottom of the screen.
        4. Cleaned up more unused code. (EXPERIMENTAL)
      13. 06/Jun/2012 - UPDATE #12
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Added CID, IMEI , BT Mac Addr and WiFi Mac Addr under Device Info (Getting WiFi Mac doesn't work correctly:( ).
        2. Revised the 'Enable/Disable ExtROM' option.
          If enabled, a partition named "null" (which will be only 1 block in size) will be created after 'userdata' and the rest 191 blocks will automatically be used for 'cache' partition .
          If disabled, 'cache' will automatically return to 5MB size .
        3. Added ability to resize partitions by giving size in blocks too . NOT TESTED
          Code:
          fastboot oem part-resize name:size:b
          where size is in blocks
          i.e. fastboot oem part-resize misc:9:b => will resize 'misc' part to 9 blocks
        4. Added ability to add partitions by giving size in blocks too . NOT TESTED
          Code:
          fastboot oem part-add name:size:b
          where size is in blocks
          i.e. fastboot oem part-add misc:8:b => will add 'misc' part with size 8 blocks (= 1MB)
        5. Added option to enable/disable usb detection ("USB" mark at the bottom of the screen if device connected to pc) .
        6. Changed version to LK_1.5black to avoid confusion regarding latest version of main cLK.
      14. 21/Jun/2012 - UPDATE #13
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. cLK can now be updated through fastboot* using a 'proper' image file**
          *:In order to update use :
          Code:
          fastboot flash lk lk.img
          **:In order to create the lk.img, use nbgen :
          Code:
          nbgen -b:lk.bin -o:lk.img
          -Note that the partition table will not be overwitten.
          -Also you can update clk from recovery or from android.
        2. Bug fixes
      15. 20/Jul/2012 - UPDATE #14
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Added option to reset ANY settings you have modified.
          (RESET SETTINGS under SETTINGS MENU = 'fastboot oem reset' ,previously cmd was 'fastboot oem format_vptable')
        2. Fixed errors caused by some partition changes, so it should be stable now!
      16. 26/Jul/2012 - UPDATE #15
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Ported some commits from LK mainline.
          (https://github.com/travisg/lk/commit/a95146ec5aef73b49e37045f96a26c10431d37d4,
          https://github.com/travisg/lk/commit/6f28039866ddeb272e8660dd89a34208fc988896,
          https://github.com/travisg/lk/commit/fc20e231dbabecb612343aa6784705086844052f,
          https://github.com/travisg/lk/commit/ac8b88eefe9067fb0881e15435dce1bbc797d71b,
          https://github.com/travisg/lk/commit/836375f779308d868515d43fbd7979f07874b6de,
          https://github.com/travisg/lk/commit/c2a298970d74dca7c7d738b5e7e3ec04bee00984,
          https://github.com/travisg/lk/commit/c32135b7e5972ec77f0883f55dd8b866b3c07c0d,
          https://github.com/travisg/lk/commit/18559782b3335682310fdfd77b4ccb1563982d2a,
          https://github.com/travisg/lk/commit/06d781f162ff3b35f806de59d7f0bf5bf87fdabd,
          https://github.com/travisg/lk/commit/4bea031527e6d0153e61b7ffd4696df8a30f006c)
        2. 2nd attempt at fixing errors caused by some partition changes.
        3. Edited nbgen so that it is possible to add recovery as a second partition.
      17. 11/Sep/2012 - UPDATE #16
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Added option to set the default boot partition. At start default is 'boot', but you can change it.
        2. Added option to show or not a MULTIBOOT MENU at startup. Default behavior is to be hidden.
        3. The MULTIBOOT MENU will show any existing boot partitions
          and will boot from the default selection in 10s if you don't select something else.
        4. Code:
          supported_boot_partitions[] =
          {
          	{"boot",},
          	{"sboot"},
          	{"tboot"},
          	{"vboot"}, //no uboot :D
          	{"wboot"},
          	{"xboot"},
          	{"yboot"},
          	{"zboot"},
          	{""},
          };
          As you see we have the primary boot + 7 extra boot partitions.
          However there is NO change to the MAX_NUM_PART (max number of the partitions) which is 12, so you can eventually add 5 (of the 7 extra) different boot partitions,
          (unless you don't have a NAND installation and you have deleted 'system' and 'userdata' so you can use all 7 extra, but I think it will be a mess :p).
        5. Added ability to control menu navigation through fastboot:
          Code:
          'fastboot oem key 8' ==> KEY_VOLUMEUP
          'fastboot oem key 2' ==> KEY_VOLUMEDOWN
          'fastboot oem key 5' ==> KEY_SEND
          'fastboot oem key 0' ==> KEY_BACK
        6. Removed option to enable/disable usb detection ("USB" mark at the bottom of the screen if device connected to pc) . By default it will be disabled .
      18. 18/Sep/2012 - UPDATE #17
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. acpuclock that Rick wrote and I managed to break:eek:, works again. So you have a new option under SETTINGS: SET MAX/DEFAULT CPU FREQ.
        2. Changed the menus. Rearranged SETTINGS and INFO and their entries.
        3. Fixed the charging while off problem that the last version had. Plus you don't need to unplug the cable in order to turn your phone on. Just press once the [CALL] button.
        4. Fixed errors regarding partition rearrangement.
          Also from that menu you can remove 'system' and 'userdata' from the partition table, by setting their order to 0. This will give you the chance to add 2 more extra boot partitions. If you went crazy and did that, but something doesn't work well, and you want back 'system' and 'userdata' you just have to RESET SETTINGS and the partition will return to default.
        5. Fixed some errors regarding add/remove %x%boot.
        6. Changed how the countdown in multiboot menu works. If you interact then the countdown is canceled.
        7. Added option whether to fill the bad block table at startup or not, FILL/SKIP FILLING BBT @ STARTUP under SETTINGS.
          Remember the option PRINT BAD BLOCK TABLE? If you don't select to FILL BBT @ STARTUP, then you won't see a BAD BLOCK TABLE because it will not be created. In simple words this means a little faster boot into cLK menu.
        8. At a (re)boot event the way LK is determining what to do is:
          First checks if any key was pressed, then checks the boot reason.
          For example, if you selected 'Reboot to bootloader' from android but in the process you want to boot to recovery, you can just press&hold the [HOME] button until the phone vibrates.
        9. Removed the function regarding auto-resizing small partitions which have bad blocks.
        10. Added a fading animation before booting any kernel or recovery.
      19. 18/Sep/2012 - UPDATE #18
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Fixed messed up menus if more than one extra boot partition exists.
      20. 20/Sep/2012 - UPDATE #19
        Code:
        [U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Fixed messed up menus if the order of the extra boot partitions is changed from default.
      21. 24/Oct/2012 - UPDATE #20
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Increased default size of 'recovery' partition to 6MB and changed layout.
        2. Removed fading effect.
        3. Added back option to enable/disable usb detection ("USB" mark at the bottom of the screen if device connected to pc).
        4. Some platform code changes.
      22. 29/Oct/2012 - UPDATE #21
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Leds work. If you boot into cLK menu and your device is connected to a pc the led will go green. If not connected the led will stay turned off.
        2. Screen brightness can be adjusted. Added option under SETTINGS. The selected level will be the default at each boot.
        3. Entering cLK menu is slightly slower than before.
        4. Added an option to change UDC settings at will. This is an attempt to solve any usb issues you might have (fastboot errors) without having to re-compile cLK's binary with different udc settings. 1st set is the default one. 2nd is the set that cLK used to have initially (1.5_rc1). 3rd is not working for me either, but left it for testing. So lets see how this goes...
        5. When in cLK menu you can select items with the [MENU] button too(added this for those with broken [CALL] button).
      23. 11/Nov/2012 - UPDATE #22
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Changed some options under SETTINGS.
        2. Added option to use inbuilt off-mode charging under SETTINGS/SET DEFAULT OFF-MODE CHARGING. From that menu you can select it (option USE INBUILT OFF-MODE CHARGING) and try it out.
          If using inbuilt off-mode charging the device wakes up if you press POWER [button].
          This is an experimental feature! Only tested with original battery and charger.
          High Voltage (as measurement) is set to 4.2 V. Use at your own risk! Otherwise stick to the default way of charging (option USE RECOVERY'S OFF-MODE CHARGING).
        3. Usb detection function changed (option under SETTINGS/ENABLE USB DETECTION). "USB" mark at the bottom of the screen if device connected to pc is replaced by turning led on/off if connected/disconnected.
        4. Added some code as an experiment for a potential off-mode alarm application.
          More info in this thread.
          Warning : I didn't know java or how to use eclipse and make an android app. Seriously, I still don't. But after some days I managed to write this application mostly because I wanted to know if this idea was possible. So consider it as an example. Any criticism accepted:eek:. I just hope that someone may find it useful and make the best out of it.
      24. 19/Nov/2012 - UPDATE #23
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
        [U]ExtRom:[/U] Disabled
        1. Added option to set the voltage threshold for inbuilt off-mode charging under SETTINGS. It can be set from 3.8 to 4.2 V.
        2. Changed the code for the off-mode alarm application based on Rick's suggestions. In order to work you need to have a patched kernel like this one. More info on off-mode alarm in this thread.
        3. Added some code for another project, a multiboot android app. More info here.
        4. Small fixes.
      25. 23/Nov/2012 - UPDATE #24
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] (a)CWM Recovery Touch Beta 8 Release Candidate 1 Or (b)TWRP 2.2.2.0 with new zImage (patched tytung's latest GB-kernel)
        [U]ExtRom:[/U] Disabled
        1. Voltage threshold for inbuilt off-mode charging can be set from 3.7 to 4.2 V.
        2. First attempt to fix problem with suspend mode.
        3. Each included recovery is edited to fix the problem with the limitation of total mtd partitions(before edit the max was 11 - now I've set it to 20).
      26. 05/Feb/2013 - UPDATE #25
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] Extended TWRP 2.4.1.0.r1
        [U]ExtRom:[/U] Disabled
        1. Fixed output for option to make an 'autosize' partition 'fixed-size'.
        2. If set to do so, fill bad block table before any flash_write will be called(like in set_recovery_message()).
        3. Add ability to change ptable according to values passed from recovery_msg.
        4. Ported commits from mainline lk.
      27. 06/Feb/2013 - UPDATE #26
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] Extended TWRP 2.4.1.0.r1
        [U]ExtRom:[/U] Disabled
        1. Changes relevant to memory offsets:
          Code:
          RAMDISK_ADDR     		:= "(BASE_ADDR+0x01000000)"
          SCRATCH_ADDR     		:= "(BASE_ADDR+0x02000000)"
      28. 11/Feb/2013 - UPDATE #27
        Code:
        [U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] Extended TWRP 2.4.1.0.r2
        [U]ExtRom:[/U] Disabled
        1. Added ability to wake the device while off-mode charging by pressing the middle [MENU] button (for those with power button problem).
        2. Updated the change_ptn_layout() function to be compatible with new Extended-TWRP.
      29. 14/Mar/2013 - UPDATE #28
        Code:
        [U]Default partition table:[/U] recovery=8,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] Extended TWRP 2.4.4.0.r1
        [U]ExtRom:[/U] Disabled
        1. Increased default size of recovery partition to 8MB.
        2. Updated the change_ptn_layout() function to be compatible with new Extended-TWRP.
      30. 6/May/2013 - UPDATE #29
        Code:
        [U]Default partition table:[/U] recovery=8,boot=5,misc=1,system=150,userdata=0,cache=5
        [U]Included recovery:[/U] Extended TWRP 2.5.0.3
        [U]ExtRom:[/U] Disabled
        1. Update get_rom_name_from_cmdline(): return NAND if cmline = "no_console_suspend=1 console=null".
        2. Update included version of recovery in nbh file.
    64
    Posts have been re-ordered, Look above.
    63


    Drivers and Utilities
    The following tools are provided here, for linux(ubuntu 64bit binaries), windows and mac:
    • adb
    • fastboot
    • mkbootimg (not windows)
    • unpackbootimg (not windows)

    Q: What is cLK?
    A: cLK is a homebrew bootloader which will allow you to boot into android directly on your windows mobile phone.

    Q: Is it better then magldr ?
    A: This question is heavily dependent on the user and his needs however the following points might help you make a better choice:
    • magldr is capable of booting Windows Phone 7.x.
    • cLK boots a tad faster than magldr as it does not wait for radio processor on boot.
    • cLK is open source so you can give/take what you want and learn stuff while doing so.
    • cLK has Partitioning tools inbuilt, you'll never have to hook your phone to a computer ever again, just for flashing a rom!
    • cLK has recovery inbuilt for users with broken usb port.
    • cLK supports off-mode charging

    • RMNET does not work.

    57
    [07 Jun 2011][BOOTLOADER]+[RECOVERY]cLK v1.4.0.1

    Contents
    Post 6: cLK compile HowTO (Linux)
    Post 7: cLK compile HowTO (Windows)
    Post 8: ROMs, HowTOs, Utilities (created by others)
    Post 9: convert magldr ROM to cLK HowTO


    Source code


    Drivers and Utilities
    The following tools are provided in here, for linux(ubuntu 64bit binaries), windows and mac; thanks to Segnale007, who compiled them for mac.
    • adb
    • fastboot
    • mkbootimg (not windows)
    • unpackbootimg (not windows)
    50
    cLK v1.5
    Check first post for information.

    You're free to mirror it, but possibly include a link to this thread incase of future updates.