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.
I was curious if it was possible to use a kernel that was developed for the LG G2X or LG Optimus 2X? Which have the cortex a9 cpu and same tegra 2 gpu. Only difference is the internal memory is different, the LG phones have the 800x480 display and only 512MB of ram. However can it be done? Has Anyone tested them?
Don't comment if you haven't tried it or don't have a solution. I want solutions from people who have attempted this. Not people simply saying it won't work. If you are going to say No, it won't work. EXPLAIN WHY!
Would someone be able to explain why other tegra 2 cortex a9 kernel's wouldn't work on the tegra 2 cortex a9 motorola atrix?
Thanks
Kernels are compiled with all the device drivers for the specific device, and for the memory partitioning of the device. A kernel for a G2X or O2X will not work on an Atrix. Nobody is going to try it because most likely the phone would be bricked (i.e., not power on at all and be dead to the world).
Will the kernel for a G2x even work on an O2x, or the reverse??
just to reafirm
jboxer said:
Kernels are compiled with all the device drivers for the specific device, and for the memory partitioning of the device. A kernel for a G2X or O2X will not work on an Atrix. Nobody is going to try it because most likely the phone would be bricked (i.e., not power on at all and be dead to the world).
Click to expand...
Click to collapse
I know people like multiple answers before they accept it.
Kernels are phone specific. donot try flashing a kernel for a different phone on any other phone it wont be pretty.
But with the atrix bootloader unlocked now. im sure there must be development on kernels for it.
there are kernels in this link below. if there is a feature they dont have that you want just politely ask them if its possible.
http://forum.xda-developers.com/forumdisplay.php?f=997
Just wanted to say I already tried and low and behold it actually works just fine. Installs without a problem. Upon reboot the phone is within the deepest most devastating hard brick known to man. LOL just kidding! It worked fine and then I restarted system and it booted into the OS without an issue resulting in absolutely no change to the system. Still detected previous kernel.
1chris89 said:
Just wanted to say I already tried and low and behold it actually works just fine. Installs without a problem. Upon reboot the phone is within the deepest most devastating hard brick known to man. LOL just kidding! It worked fine and then I restarted system and it booted into the OS without an issue resulting in absolutely no change to the system. Still detected previous kernel.
Click to expand...
Click to collapse
well thats good that it didnt actaully flash the kernel because i can guarentee you that a kernel for the g2x will not work with another phone. just make sure you alsways have a working kernel on your sdcard if you try others so you can revert back easily.
for future reference i really dont understand why you posted a question when you are going to ignore the answers.
Just glad it didnt really flash.
the days i was walking along the internet to get some informations about lapdock/webtop again
like often it kicked me back to the roots -> XDA http://forum.xda-developers.com/showthread.php?t=2588623
there is a patch to make space for a second system
iam sure thats a way we can install webtop on our phone.
but i not wanne try it first ;] cant buy me a new phone if something goes wrong
and it need to be modifyed first
what do you think? its the right way?
I think due to the fact that Photon Q uses Qualcomm architecture instead of TI's, maybe it doesn't even support BMM. At least I've only seen BMM running on TI OMAP-powered devices so far.
Sent from Google Nexus 4 @ CM11
I would love to see a boot Manager on our phone.
That would give me more freedom to test different ROMs.
But theoretically we need to be able to change/add/remove partitions for this.
Afaik this is not possible, so there probably won't be any boot manager.
Hey guys. I tried to port CyanogenMod for my ZTE Blade III Pro ( copy/paste tutorial ) because there is no kernel source for this phone and there are no custom roms for it. It's a MSM8225 device ( 2 cores 1GHz, 512mb RAM, 4" display, 4.1.2 android .... ) I'm a big fan of AOSP and vanilla android so I tried to port cyanogenmod 10(4.1.2) from Huawei Y300. I did all the steps, repackaged the files into a zip archive, installed it with CWM and expectedly ran into bootloop. The phone won't go past the bootanimation. I did a logcat and there are several fatal errors (signal 11) I've searched and I found that this error is being caused because of the kernel (boot.img), and can be solved with flashing the kernel-only after installing the ROM through the recovery. So my question is: What will happen if I try to flash the cm10 kernel made for the phone I tried to flash the CM10 from (Ascend Y300)??? I'm not really sure what will happen, but since they have the same internals (http://www.gsmarena.com/compare.php3?idPhone1=5425&idPhone2=5386) it should work. But I bricked this phone once (different reasons) and they had to replace the main board ( chipset probably ) but luckily I didn't have to pay anything. Will I be able to flash my stock kernel if this won't help booting the ROM??? Is there a possibility that the phone will be bricked that I will have to replace the chipset??? Please help me.
1. Read the stickies
2. You should never flash a port from any device unless you know what you're doing. Even more so if you ported it yourself. You may want to just go back to stock, but since you said there are no kernel sources, I'm guessing there is no way to return to stock, ergo, you might be SOL.
Vuciz said:
1. Read the stickies
2. You should never flash a port from any device unless you know what you're doing. Even more so if you ported it yourself. You may want to just go back to stock, but since you said there are no kernel sources, I'm guessing there is no way to return to stock, ergo, you might be SOL.
Click to expand...
Click to collapse
Well, I actually know what I'm doing, and that it's very risky, and I've flashed ported ROMS like this before, and they never worked, so I know how to recovery from a soft-brick(bootloop), but I didn't know what would happen If I tried to flash kernel made for a totally different phone. But you seem to know quite a bit about Android porting, and I wanna ask you another question. Even though ZTE hasn't released kernel-source for ZTE Blade III Pro (my device), it has released sources for ZTE Blade G, which has the same internals as ZTE Blade III Pro, but features a bigger and higher resolution display!!! http://www.gsmarena.com/compare.php3?idPhone1=5425&idPhone2=5620 Can I use the kernel source to attempt to build cyanogenmod or a completely stock ROM from source??? I know how to do this because I've already been doing it but failed when I came to the step to load the sources. But, still, I'm sure that the display wouldn't work. Thanks anyways...
I've ported from the G300 to the Fusion 2, and you still need to use a modified kernel so it works on your device.
You should also note that while the first two devices have similar specs they are from different OEMs so they could be totally different. Also when porting the displays must have the same res.
Vuciz said:
I've ported from the G300 to the Fusion 2, and you still need to use a modified kernel so it works on your device.
You should also note that while the first two devices have similar specs they are from different OEMs so they could be totally different. Also when porting the displays must have the same res.
Click to expand...
Click to collapse
Thanks again!!!
hi guys,
When i see this forum there is not a lot of development. i rooted the phone but i am looking to install a custom recovery on my g flex 2, but i can not find anything about that on this forum (probably because it is so new). so i wondered could i check the g flex 1 forum for a custom recovery or would this just destroy my phone?
BZander said:
hi guys,
When i see this forum there is not a lot of development. i rooted the phone but i am looking to install a custom recovery on my g flex 2, but i can not find anything about that on this forum (probably because it is so new). so i wondered could i check the g flex 1 forum for a custom recovery or would this just destroy my phone?
Click to expand...
Click to collapse
The safest rule to live by is to never flash anything designed for one phone to a different phone. While they are both made by LG and both have the name Flex on them, they are completely different in hardware. Flashing the recovery of one phone to an unrelated phone could even brick your phone.
Flash it and check
Sent from my LGLS996 using xda Forum
Hmmmm i guess we'll kust have to wait.
Alwats thought recovery on your phone was something like a BIOS in your pc and Android was the Windows.
Guess i was wrong.
Hope someone makes a recovery than.
You're not that far off, but to extend the analogy you're asking to flash a Pentium 4 BIOS onto an i7 motherboard.
The recovery is technically a "ROM" in itself. It has a kernel compatible with the hardware, drivers for the hardware, and the partitioning scheme of the hardware, among other things.
While it's based on the Linux Kernel, Android (and most ARM based Linux) does not build global images that work with every device. This is for several reasons:
1. It wasn't even possible until relatively recently. (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9cd11c0c47b8690b47e7573311ce5c483cb344ed http://www.phoronix.com/scan.php?page=news_item&px=MTE5ODI
2. Embedded devices have limited storage. Historically, this meant that saving every kb of storage was very important and thus kernels were and are compiled only with the code that is needed for the specific device being used.
3. OEMs do not use a global source code. They fork their version of the Android Linux Kernel fork for each and every single device. Making changes to the source code for a single device without breaking other devices can be tedious so OEMs do what they can with the time constraints that they have.
Of course, I could be very wrong, but that is my understanding of it.
Any news on a recovery for G Flex 2?
I'm wondering if anyone has had any luck finding a recovery that will work on the G Flex 2, I found something called clockworkmod builder (cannot post a link because I am too new) but don't know enough yet to use it, or if it will even work.