[23 Nov 12] cLK

Search This thread

Hammerfest

Senior Member
Apr 3, 2008
1,683
287
San Antonio, TX
yeah the only thing I can think of is that cotulla sees cLK as too much of a opponent to his solution, instead of caring for the community and having the best stability/functionality he says NOPE MINE BUGGER OFF (then stops updating things and moves on leaving everyone/thing in the dark without releasing anything)

other then my rant, I cant wait to see more cLK development, for me personally I see more stability with HSPL 3.03, so cLK was my option, and so far, it works wonderfully! Issues with rom's and data aside, cLK has been my best option!
 

siddharth singh

Senior Member
Oct 9, 2009
383
44
kolkata
yeah the only thing I can think of is that cotulla sees cLK as too much of a opponent to his solution, instead of caring for the community and having the best stability/functionality he says NOPE MINE BUGGER OFF (then stops updating things and moves on leaving everyone/thing in the dark without releasing anything)

other then my rant, I cant wait to see more cLK development, for me personally I see more stability with HSPL 3.03, so cLK was my option, and so far, it works wonderfully! Issues with rom's and data aside, cLK has been my best option!

If cotulla wouldn't had been there... Android wouldn't had been on hd2 i think... Correct me If I'm wrong

Sent from my HTC HD2 using XDA App
 

LiFE1688

Senior Member
May 7, 2010
385
80
yeah the only thing I can think of is that cotulla sees cLK as too much of a opponent to his solution, instead of caring for the community and having the best stability/functionality he says NOPE MINE BUGGER OFF (then stops updating things and moves on leaving everyone/thing in the dark without releasing anything)

other then my rant, I cant wait to see more cLK development, for me personally I see more stability with HSPL 3.03, so cLK was my option, and so far, it works wonderfully! Issues with rom's and data aside, cLK has been my best option!

Hmm... no Cotulla and/or Darkforce Team, then no HSPL, no MGLDR, then there wouldn't be cLK either.

I am guessing, Cotulla might have HTC inside information. Any information exchange such as how MGLDR supports rmnet might trace back to the leak. Therefore MGLDR and HSPL is closed source.
 
Last edited:

Hammerfest

Senior Member
Apr 3, 2008
1,683
287
San Antonio, TX
Hmm... no Cotulla and/or Darkforce Team, then no HSPL, no MGLDR, then there wouldn't be cLK either.

I am guessing, Cotulla might have HTC inside information. Any information exchange such as how MGLDR supports rmnet might trace back to the leak. Therefore MGLDR and HSPL is closed source.

I am not ignoring the fact that w/o them in the first place, it PROBABLY wouldn't exist.

Additionally, if your saying that because its reverse engineered or made from "inside information" and that sharing it might get them in trouble, well correct ME if im wrong, but isnt like saying someone who robs a bank wont get in trouble until they spend or give away the cash they stole... and that's a pretty close comparison as far as i can tell... but its still bull**** through and through.

The reality of the situation is more like: we did the work, we want to keep the glory, find another way yourself... or something similar, again if you reverse engineer something your still in trouble (robbing bank), just because you don't share the source with anyone else doesn't mean you still aren't liable or as guilty as if you do share (make purchases or give free cash out)...
 
Last edited:

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
nope, i don't believe that this is the case. it's more to do with the hack he applied (loading radio parts of desire into leo radio rom). this really is dangerous and can brick your device, if done wrong; and there are facts which are telling that this is true.
 

j45p41

Member
Jan 8, 2010
41
1
London
nope, i don't believe that this is the case. it's more to do with the hack he applied (loading radio parts of desire into leo radio rom). this really is dangerous and can brick your device, if done wrong; and there are facts which are telling that this is true.
Hi Guys,

i have a HD2 with faulty USB port. I have HSPL 2.08 installed. What would be the steps to install NAND rom via CWM with CLK?

I was hoping that this release would allow it as for the last one you need usb to flash CWM.....

please help :):)
 

j45p41

Member
Jan 8, 2010
41
1
London
if you find a way to install with clk and recovery at once from sd card method (leoimg.nbh) it would be awesome to be able to change on the road between wm and nand android
Hi Guys,

i have a HD2 with faulty USB port. I have HSPL 2.08 installed. What would be the steps to install NAND rom via CWM with CLK?

I was hoping that this release would allow it as for the last one you need usb to flash CWM.....

please help :) :) :)
 

clyder

Senior Member
Aug 30, 2010
1,060
475
Indjija
Hi, I just switched to cLK yesterday and so far it is working OK.
I had terrible data drops with beta5 wrapper but with beta4 I haven't experience any.

But download speed in market is much slower than in magldr(rmnet) version of the rom I am using (Hyperdroid). Speedtest gave me an average of 200kbps, but in market download goes about 30-40 kbps. Is this normal behavior in cLK or this could be an rom issue?
 

mwakious

Senior Member
Jan 24, 2008
2,451
6,724
mwakiousromseries.webnode.it
Hi, I just switched to cLK yesterday and so far it is working OK.
I had terrible data drops with beta5 wrapper but with beta4 I haven't experience any.

But download speed in market is much slower than in magldr(rmnet) version of the rom I am using (Hyperdroid). Speedtest gave me an average of 200kbps, but in market download goes about 30-40 kbps. Is this normal behavior in cLK or this could be an rom issue?

beta5 gave me trubbles to,in one rom i found it working well GB 2.3.4(TyphooN CyanogenMod 7)all the others go with beta4.

the market speed is not a good example for mesuring the speed,i have clk from the first day that its out and i can say that with all roms that i use the same thing happend --> there are days that the market its self goes very slow<-- it maybe server related,see in browser your speed or change the rom(just to verify).
o!one more thing,tytungs kernel 10 has a little problems with clk,my opinion after testing,try version 9 its a lot better

one question for arif:because i dont remember and i cant find it,what is the changes from beta1 to beta4?
 
Last edited:
  • Like
Reactions: clyder

clyder

Senior Member
Aug 30, 2010
1,060
475
Indjija
beta5 gave me trubbles to,in one rom i found it working well GB 2.3.4(TyphooN CyanogenMod 7)all the others go with beta4.

the market speed is not a good example for mesuring the speed,i have clk from the first day that its out and i can say that with all roms that i use the same thing happend --> there are days that the market its self goes very slow<-- it maybe server related,see in browser your speed or change the rom(just to verify).
o!one more thing,tytungs kernel 10 has a little problems with clk,my opinion after testing,try version 9 its a lot better

When I experience slower market I tried to use wifi instead of mobile data and it went faster. After that I disabled wifi and market got slower again. But just now I tried downloading something on mobile data and it went much faster.

About the kernel, thanx for the suggestion. I will try it.
BTW, what king of issues you had with r10? Besides this thing with market I haven't seen anything wrong so far.
 

clyder

Senior Member
Aug 30, 2010
1,060
475
Indjija
hadrware keys except not working properly

hi, after a reboot I stumbled upon one issue that I cant solve.
Suddenly my hardware keys are not doing anything. I can use power button to wake device and turn the screen of. The rest of the buttons I can use only to wake the device. In system all they do is light up the buttons. I tried deleting the cache/dalvik/data, installed the rom again without restoring anything or installing any additions, did that with several other roms, installing tytung r9 kernel but everytime it boots they dont work.

I am at work now so cant really reinstall cLK or magdlr.
Any help is more then apritiated.
 

clyder

Senior Member
Aug 30, 2010
1,060
475
Indjija
hi, after a reboot I stumbled upon one issue that I cant solve.
Suddenly my hardware keys are not doing anything. I can use power button to wake device and turn the screen of. The rest of the buttons I can use only to wake the device. In system all they do is light up the buttons. I tried deleting the cache/dalvik/data, installed the rom again without restoring anything or installing any additions, did that with several other roms, installing tytung r9 kernel but everytime it boots they dont work.

I am at work now so cant really reinstall cLK or magdlr.
Any help is more then apritiated.



After doing the task29, reinstall of cLK and recovery I flashed an fresh rom and everything was OK. After restoring data in CWR problem was there again. After another data wipe it was OK again. But first time I had this problem I did about 5 data/cache wipes and installed fresh rom (several of them) with the issue.

So now I am not sure if that was rom issue, cLK or whatever, but important thing is that it works. Now I only have to find a way to extract data for some stuff from previous backup.
 

clyder

Senior Member
Aug 30, 2010
1,060
475
Indjija
I located what was causing my hardware keys issue.
I flashed GB234_GpsLocationProvider_JNI_fix_update.zip from tytung gps libs page.
As soon as I reverted the file that was originaly in rom the problem went away.
This file never gave me any problems while I was on magdrl....
 

cherni

Member
Sep 12, 2008
49
6
Hi All,

I have constant problems with my mobile data connection with CLK. Using libhtc_ril_wrapper_0.8b4_CWR.zip, If I turn on WIFI and then off, the data connection does not restart. Also this happens when I receive a call.

Now, with libhtc_ril_wrapper_0.8b5_CWR.zip, this does not happen, but the data connection is too unstable. When I use skype or any high demanding internet connection, it drops.

Any one having the same issue?

Cheers!
 

clyder

Senior Member
Aug 30, 2010
1,060
475
Indjija
Hi All,

I have constant problems with my mobile data connection with CLK. Using libhtc_ril_wrapper_0.8b4_CWR.zip, If I turn on WIFI and then off, the data connection does not restart. Also this happens when I receive a call.

Now, with libhtc_ril_wrapper_0.8b5_CWR.zip, this does not happen, but the data connection is too unstable. When I use skype or any high demanding internet connection, it drops.

Any one having the same issue?

Cheers!

I only had issues with b5. With b4 in Hyperdroid data is super stable for me. In the last few days since I switched to cLK I havent noticed any data drop.
Also just tried to turn wifi on and off and data connection went back and workng few seconds later.
 

cherni

Member
Sep 12, 2008
49
6
I only had issues with b5. With b4 in Hyperdroid data is super stable for me. In the last few days since I switched to cLK I havent noticed any data drop.
Also just tried to turn wifi on and off and data connection went back and workng few seconds later.

Mmmm let me see how Hyperdroid works!
 

mkamodang

Senior Member
Jun 3, 2010
108
12
India, New Delhi
I would like to install/replace my present wrapper with 0.8b5 since I am getting data drop in GBX 12 rom. Kindly show me step by step method of installing it. I am using clk as my bootloader. Thanks
 
J

j4n87

Guest
I would like to install/replace my present wrapper with 0.8b5 since I am getting data drop in GBX 12 rom. Kindly show me step by step method of installing it. I am using clk as my bootloader. Thanks

take the beta5 cwm.zip from my signature, go into rom manager, browse to that zip and install it.

...if you didn't use rom manager before you can also reboot your phone and hold down the home button.
It should boot into recovery, then choose install from zip-chose zip from sd card, browse to the file and confirm with yes.
 

cherni

Member
Sep 12, 2008
49
6
I only had issues with b5. With b4 in Hyperdroid data is super stable for me. In the last few days since I switched to cLK I havent noticed any data drop.
Also just tried to turn wifi on and off and data connection went back and workng few seconds later.

I had the same problem. I went into magdlr and did the master reset. Then everything was fine again.

Well,

Now after using both CLK and MAGDLR I can post some differences for ROM NexusHD2 latest realease:

CLK Version:

- Mobile Data connection drops, unstable or disconnects. Tried diffrent beta wrappers, but had issues anyway. With 0.8b4 data connection was stable, but when I received a call it went dead (had to switch to airplane mode and back to reset the connection). With 0.8b5 connection was unstable.

- Bluetooth*: When I turned on BT, the FTP service didn't startup automatically. I had to run the app manually. See MAG version for correct operation.

MAG Version:

- Mobile data connection stable.

- Bluetooth*: Works as it should. When I switch BT ON, the FTP service APP automatically starts and shuts down when switched off.

* Don't know if a CLK or ROM bug, but is another difference I noted!

Let's see if future versions of CLK Wrappers fix this, will be available to test :)

I believe that CLK gives the best Android experience and integration, a final fix for wrappers will make it a standard :)
 

corlygunnz

Senior Member
Sep 9, 2009
439
34
Katy
www.keypunchers.io
Anyone know of a stock desire rom that works with clk? Or a desire HD rom with data connection stable? I only use JW miui because is the only rom that I can count with my data connect not dropin. But I miss desire rom.

Sent from my HTC HD2 using Tapatalk
 

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.