Project Description
This is a project to port the Droid version of CyanogenMod to the milestone. While the Droid and Milestone devices are twins, they are CDMA and GSM respectively. Hacks include not flashing the boot image provided by the CM Droid package and some GSM configurations.
Status
CyanogenMod 6 RC1 (with CoburnROM hacks) will flash successfully, however it will refuse to boot (possibly due to incompatible stock kernel or that the milestone doesn't like unsigned ROMs). So far, flashing works from koush's ClockWorkMod Recovery and Open Recovery 1.14. When rebooted, the device hangs on the M Boot logo.
Downloads
PoC/RC #1: Download from my blog, Geek In The Family - 75MB.
What you can do
Pretty much this ROM is currently a playground, if you want to have a poke around, download a copy of the above versions of the ROM and extract it, and then poke around and see what makes it tick.
Other notes
Space saved for future use.
Cheers!
Reserved for future use
Sent from my Milestone using XDA App
Good luck man, I really hope this happens
You should check with the guys on and-developers.com, and their IRC channel #milestone-modding on Freenode for any progress on the bootloader
Hacking the bootloader is impossibile on our Milestone, the TI OMAP chipset runs in High Security mode and for switching to General Purpose mode you have to desolder and resolder the OMAP chipset on your mainboard, soldering the right pins for enabling the GP mode.
Anyway, 2ndboot can make us able to boot a different kernel (for now GSM modem is unusable, so we can't use the phone with the new?y booted kernel) and this is the way that we'll take on the Milestone for using a custom kernel.
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Sent from my Milestone using Tapatalk
kholk said:
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Click to expand...
Click to collapse
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Good luck to you. I commend you for your efforts.
After 1 year waiting for the bootloader to be hacked...I am slightly skeptical. However, now that the Droid X has been released to the masses with the same locked bootloader, we might get some fresh eyes to look into this matter.
I would be happy enough with a custom kernel running on 2nd boot ;-)
SenseUI Mod
Hello, You might try using the mot_boot_mode file, which is also used with the SenseUI Port for the Milestone, I guess that would make this boot too? If I'm right, this is the boot sequence:
This is what I'm talking about:
"the ramdisk is located in /system/ramdisk.tar folder, it all starts here.
the ramdisk is opened by /system/bin/mot_boot_mode."
You should download the SenseUI Mod and analyse it's way of booting.
Good luck!
Coburn64 said:
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Click to expand...
Click to collapse
the problem is not about being negative but you are facing it the wrong way .
the problem here is to hack the thing not to port an already existing mod .
Once the bootloader is bypassed they ll be hundreds of real ROMS .
Anybody can pretend at porting there own roms it is completely IRRELEVANT since it wont be possible until its hacked.
you said it 'even if I have to wait ' well there you go do like thousands of others and just wait . BUt please dont pretend at anything else , thank you .
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
So you're not going with that 2ndboot method?
In any case, my eyes are glued to your twitter account
Coburn64 said:
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
Click to expand...
Click to collapse
dude your my hero
It's kinda off-topic, but I just thought, why don't we go 4chan style on Motorola, and, for example, black fax local Motorola offices or something?
Coburn64 said:
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Click to expand...
Click to collapse
As I said, it IS possible to skip the BL checks, and it's fully hackable...but...I know.... you don't want to resolder your OMAP....
if this mod is "Droid" based, you need to make many modifications to the startup..
the Droid is in no way protected, where Milestone has GSM radio protected, and specific drivers required to open it, which for now only opens when using the original "init" process of a milestone.. the "init" from droid disables radio completely..
but take a look on how i got the senseui port running.. i got the froyo partly running the same way, so im sure my solution used in senseui mod will help you along to make it work...it just requires some debugging and "adb logcat" so you at least can see what happens at startup..
why not work together dexter? i think this may help out in particular cases
Dexter_nlb said:
if this mod is "Droid" based, you need to make many modifications to the startup..
the Droid is in no way protected, where Milestone has GSM radio protected, and specific drivers required to open it, which for now only opens when using the original "init" process of a milestone.. the "init" from droid disables radio completely..
but take a look on how i got the senseui port running.. i got the froyo partly running the same way, so im sure my solution used in senseui mod will help you along to make it work...it just requires some debugging and "adb logcat" so you at least can see what happens at startup..
Click to expand...
Click to collapse
DO YOU HAVE FroYo running!?!?!?!??!?!?!?!?
Coburn64 said:
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
Click to expand...
Click to collapse
I never said you were lying all I said was dont pretend ' about rom ' when even a basic kernel wont run .
if you have a workin kexec would you mind sharing it ?
I'm very interested in your work since it seems that we will never see an official 2.2 from Motorola... I don't know if we are going to have the new update, here in France (2.1 update 2).
Well, I just have a question. On a french forum, someone posted a method to downgrade the ROM of the Milestone by implementing the right version of the bootloader in it, I don't know if I very clear. This member had some major problems with the 2.1 update so he decided to downgrade to 2.0.1. However he wasn't able to do it because his Milestone was using the 90.78 bootloader while the 2.0.1 rom was using the 90.73 bootloader. Eventulally, he managed to install the 2.0.1 rom on his Milestone by putting the 90.78 bootloader in the 2.0.1 rom.
So my question is : will it be possible put a bootloader in a custom rom in order to make it boot on the Milestone ?
(I would give you the link for the topic on the french forum once my account si verified)
kholk said:
Hacking the bootloader is impossibile on our Milestone, the TI OMAP chipset runs in High Security mode and for switching to General Purpose mode you have to desolder and resolder the OMAP chipset on your mainboard, soldering the right pins for enabling the GP mode.
Anyway, 2ndboot can make us able to boot a different kernel (for now GSM modem is unusable, so we can't use the phone with the new?y booted kernel) and this is the way that we'll take on the Milestone for using a custom kernel.
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Actually this is a wrong assumption. HS chip cannot be turned to a Generag purpose.
For those who are interested, here is kexec.
Devs should know the drill, insmod kexec.ko etc etc.
Originally made by Kiljacken (compilation, etc), shared by me.
As for the Android 2.0.1 on Boot Loader 97.73, he may have just made a custom update zip that nukes the system partition and installs 2.0.1 on the device.
Also, I updated my Boot Loader to 90.78ch, which is the XT702 Boot Loader - no bricks. Yet.
Has anyone successfully cooked on Swift Star??? I am super familiar with UOT KITCHEN and for some reason every time I try to flash it goes through says its applying the framework but the end result is always a bootloop...I have used the kitchen on virtually every other rom with no issues Im super confused
is like he said you have to put the zip on the the clockwork/backup on your sd card then reboot into recovery full data wipe and cache wipe then go to restore and choose the zip file there enjoy !!
Ek07 said:
is like he said you have to put the zip on the the clockwork/backup on your sd card then reboot into recovery full data wipe and cache wipe then go to restore and choose the zip file there enjoy !!
Click to expand...
Click to collapse
this post makes no sense. you don't seem to understand the OP or know what you're talking about (you don't install zip files through the restore function in cwm).
to the original poster, I have only used the UOT Kitchen to customize the boot animation on my Swift star ROM but it worked fine for me. Maybe try changing one category (like just battery icons or fonts) at a time and see if you can get any further.
Good luck
hmm ok thats a good idea.Ill give it a go and see if that works.Thanks for your post..hopefully I dont get another boot loop..I heard others getting boot loops as well I will post my results as soon as I cook and flash again.
Same result..Stupid Boot loop..If anyone could give me the details of what they are doing different to get it to work I would appreciate it..its frustrating to say the least...
frescoraja said:
this post makes no sense. you don't seem to understand the OP or know what you're talking about (you don't install zip files through the restore function in cwm).
to the original poster, I have only used the UOT Kitchen to customize the boot animation on my Swift star ROM but it worked fine for me. Maybe try changing one category (like just battery icons or fonts) at a time and see if you can get any further.
Good luck
Click to expand...
Click to collapse
well i was talking to androidDude21 about why he got a boot loop u seem not to understand his question , thats how you intall that rom he is asking about ok
Sorry eko7 but i think he already has installed the ROM and just needs to know why when he alters it with UOT kitchen he is getting boot loops. Didn't mean to offend. I admit I came off sounding like an ass.
androiddude- I just tried changing the battery icon with UOT kitchen on my swift ROM and also got the boot loop. wish I was savvy enough to debug the issue. Let us all know if you make any progress. I would really like a battery icon that also shows the % of charge in this ROM.
Running out of Ideas
Yeah I definitely already installed the rom..lol I dunno how that was even in question...not to be rude.. but yeah I have tried numerous times the only thing I can think of is maybe I have to upload the touchwiz files too even though I dont use it..its a long shot but when someone asked about it the Dev said that any mods can be made in UOT kitchen..Unfortunately I don't have enough posts to post a direct question to the Dev in that forum . I like Swift Star a lot but at this point I might just give weapon 2.6 a go because I know you can definitely take that to the kitchen..Its a shame though cuz I really Like this Rom.
ok sorry im new at this but im learning sorry i dont speak all that geeky language lol but my question is are ya tryna customize the rom you own way right??
frescoraja said:
Sorry eko7 but i think he already has installed the ROM and just needs to know why when he alters it with UOT kitchen he is getting boot loops. Didn't mean to offend. I admit I came off sounding like an ass.
androiddude- I just tried changing the battery icon with UOT kitchen on my swift ROM and also got the boot loop. wish I was savvy enough to debug the issue. Let us all know if you make any progress. I would really like a battery icon that also shows the % of charge in this ROM.
Click to expand...
Click to collapse
i know how to change the battery icon is easy just use seven zip the png icons are on the system\framework\framework-res.apk\res\drawable-hdpi\
yeah basically i just wanted my overscroll glow to be blue, change my download bar and loading icon to blue as well to match the rom but every time I try even one at a time I run into a bootloop so I PM'd the Developer hopefully he gets back to me and ill post what he says..
Okay, so here's my dilemma. Unlike most other people I want boot sound enabled on my ROM's. I have spent countless hours searching every forum and post, trying everything that is suggested. Nothing seems to work. The only breakthrough I've came across the last several months is that while running a ROM with boot animation support and a stock kernel I am able to achieve both custom mods. What I'm shooting for is to be able to do the same with a custom kernel. I'm relatively new to this but through process of elimination I have concluded that the coding for this lies in the boot image. Maybe I'm wrong but it seems that way.
Listed under the features in almost every single ROM the developer usually puts "muted boot sound" my question is, how do I un mute the sound? Is there a simple fix, possibly a script that I can run or does it involve pulling apart the boot image and editing code? If it has to do with the boot image could somebody possibly tell me what code needs to be edited. I have no problem decompiling and recompiling boot images, I'm just not sure what part of the code needs to be added. Any help would be extremely appreciated! I'll keep my fingers crossed!
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Okay, so here's my dilemma. Unlike most other people I want boot sound enabled on my ROM's. I have spent countless hours searching every forum and post, trying everything that is suggested. Nothing seems to work. The only breakthrough I've came across the last several months is that while running a ROM with boot animation support and a stock kernel I am able to achieve both custom mods. What I'm shooting for is to be able to do the same with a custom kernel. I'm relatively new to this but through process of elimination I have concluded that the coding for this lies in the boot image. Maybe I'm wrong but it seems that way.
Listed under the features in almost every single ROM the developer usually puts "muted boot sound" my question is, how do I un mute the sound? Is there a simple fix, possibly a script that I can run or does it involve pulling apart the boot image and editing code? If it has to do with the boot image could somebody possibly tell me what code needs to be edited. I have no problem decompiling and recompiling boot images, I'm just not sure what part of the code needs to be added. Any help would be extremely appreciated! I'll keep my fingers crossed!
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
see my post in andybone's mod thread. you need an edited volumedb in system/etc folder where the volume is raised. i think they just set the volume level in the db to 0 and the file i posted raises it so you can now hear sounds. confirmed to work on CR6.2 by myself. oh and you will need a PowerOn.ogg in system/media/audio/ui folder... hope it helps!!:highfive: