[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Please Help out the Canadians ;)

Hey guys,

I'm from Canada, and have an SGH-I757M which is the closest to your SGH-I727 (skyrocket). There is a relatively small group of us up here that own these fancy GS2 HD LTE devices that are aching to have a copy of CM10.1 for our phones. We have a version of CM9 and CM10 done by XDA Senior Member dsixda. He has since retired this phone and no longer takes care of these ports on our device, and there seems to be no other developer up here in Canada with this phone that wants to put forth the effort needed to port this new rom to our device, so I have reluctantly tried to take on this task even though I really don't have much experience with linux/c/c++.

I have studied dsixda's work and taken note of what he had to change to get CM10 working on our phone, and think I may have somewhat figured out how I can compile 4.2 for our I757M. I do have a couple of questions though since my device is my daily driver, and am very scared to hard brick it.

I understand that in JB 4.2, the storage layout has changed, what takes care of this migration... CWM? I know I need to build and flash a new CWM, but this is what scares me the most since it requires that I use odin to flash it and I'm not sure how to ensure that my newly built CWM isn't going to hard brick my phone since without CWM, your screwed (right?).

The repos created by dsixda for my phone (SGH-I757M / Bell Canada / celoxhd) can be found here:

http://github.com/dsixda

He had to make special customizations in the following repo (most of which were taken from the skyrocket) android_device_samsung_celoxhd and added our vendor proprietary stuff in this repo android_vendor_samsung_celoxhd

Our local_manifest.xml looks like this:

<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" revision="cm-10.1" />
<project name="titanic-fanatic/android_device_samsung_celoxhd" path="device/samsung/celoxhd" revision="cm10.1" />
<project name="titanic-fanatic/android_vendor_samsung_celoxhd" path="vendor/samsung/celoxhd" revision="cm10.1" />
</manifest>

The only thing I modified in this file is that I added the repo for android_device_samsung-qcom-common (compiling complained about not being able to find these files, so I added them) and changed the revision from "jellybean" to "cm-10.1".

The last thing I did, was to change our --ramdisk_offset, but I'm very confused by this... I don't know anything about hex except for the fact that I use hex codes to represent colors in various languages. I ran both my stock boot.img and the boot.img pulled from our CM10 Rom through unmkbootimg to get the new offset, and they both provide me with different offsets... When I use the stock boot.img I get the same offset as the skyrocket --ramdisk_offset 0x01400000, but when I use the boot.img from our CM10 rom, I get this offset --ramdisk_offset 0x01500000. Which should I use? If I use the wrong value, could that cause a hard brick?

Bottom line, I have it compiling all the way through ;) I'm just scared to flash the new CWM... If a bad CWM was compiled for my phone and I flash it, does that affect my ability to boot into download mode to re-flash a good recovery image?