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.
Hello.
I'm using mini tablet, unknown brand, chip is rk2928.
I flashed two ROMs on the device, none of them with touch.
I guess I need driver or something, but don't really know what to do.
Any help?
Which ROMs did you flash?
You should flash ROMs specially made for your device, not for any other device.
Even flashing a ROM for a different carrier version of the same device can cause serious problems (AT&T Note 2 ROM on International Note 2 for example)
You will need to re-flash the Stock ROM for your tablet.
Mashed_Potatoes said:
Which ROMs did you flash?
You should flash ROMs specially made for your device, not for any other device.
Even flashing a ROM for a different carrier version of the same device can cause serious problems (AT&T Note 2 ROM on International Note 2 for example)
You will need to re-flash the Stock ROM for your tablet.
Click to expand...
Click to collapse
He is talking about a Tablet with a specific chip, for these chinese tablets, the brand does not matter, its the chipset can flash any roms that are for that chipset only.
Hello.
I'm using mini tablet, unknown brand, chip is rk2928.
I flashed two ROMs on the device, none of them with touch.
I guess I need driver or something, but don't really know what to do.
Any help?
Click to expand...
Click to collapse
your right you have to flash a touch driver, it sucks to try to find it so i am unable to help you though its normal that if the touch does not work you would have to find a touch driver, you have done nothing wrong its just these chinese chipsets suck to develop for.
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.
Hello everyone.......... So lets begin from the starting. I have recently bought an iphone x clone device. I thought it will have good enough hardware compared to its price but unfortunately it only has attractive outlook finishing but inside its really bad. I cant even watch youtube videos because of hang & crash. So I decided to root it and install ram expanding software to create vram which really helped solving the crashes....... But still the device feels laggy so I was thinking about installing a soft custom rom which will consume less rom & ram. I tried to backup my stock recovery and install a twrp custom recovery via different apps like flashify, mobile uncle tool, twrp manager etc. But all of them failed to create a backup or even flash a recovery. I had to try different custom recovery image as my device is clone and not included inside twrp supported device list. I even downloaded my stock recovery from internet (not 100% sure if its the right one but tried my luck as I couldn't collect a backup copy of my stock recovery from adb) and tried to port with other custom recoveries and install it...... But still all I boot into is my chinese stock recovery which is useless for me. After trying 2 days I have done everything I could and couldn't get further than rooting and installing some useful apps to make my device little bit stable. But this isn't enough, I need help now to find correct custom recovery and soft custom rom for my device.
Here are some pics about my device details which will help you get some idea about which device im using. drive.google.com/drive/folders/1ieMNTSkgTAIWNn1xNSqg2iCzUPXheEdI?usp=sharing
really very disappointing......... its been more than a week and i got no help from a large active tech community like xda
Khaled786 said:
really very disappointing......... its been more than a week and i got no help from a large active tech community like xda
Click to expand...
Click to collapse
Lol, it's because you have an unsupported cloned device that has no actual stock source or stock firmware to work with, it has a firmware that has been hacked together. Ask yourself why it has hacked software, it is because there is no real software for this device other than what they hacked together when they made it. I doubt you'll find anything that can be installed "as-is", you'll have to do the same thing the device maker did, you'll have to put your own software together which will require either building a whole new ROM for your device or it will require porting an existing ROM to work on your device.
It is very difficult to identify cloned hardware and very difficult to find compatible software.
And this is a "large active tech community" but most members here don't have/own/use/buy or have experience with cloned devices because we know they are junk, regardless of the specs, we have better sense than to waste our time and money on them.
Sent from my LGL84VL using Tapatalk
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
N
shadow460 said:
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
Click to expand...
Click to collapse
Not without porting them from one to the other, "IF" the sources to do so are available(either stock firmware for the two devices or at least the stock source code for the device the ROM will be flashed on.
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
shadow460 said:
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
Click to expand...
Click to collapse
There really isn't a 100% all in one get it right the first time guide out there. There are lots of guides that give a general idea of how to port stock ROMs but it will still require trial and error to iron out the details. Do some research to see if there are any specific security features preventing the ported ROM from flashing/booting then see if there are any tricks to bypass those specific features. You may need to unlock the bootloader and dig into trying to modify the bootloader.img located in the copy of your devices currently installed stock firmware file(or the last "official" firmware that was installed on your device before you tried to modify it).