Hey guys.
I know this is a question that probably belongs in Dev, but I don't have enough posts to create a thread there.
Has anyone ever tried daisy-chain booting the motorola milestone? Say, have the phone boot the proprietary Motorola kernel, which I'm pretty sure is what is checked by the hardware bootloader, and then have the motorola kernel boot up a CyanogenMod kernel? I'm pretty sure using one kernel to boot another is more or less possible with desktop linux kernels, why not on android kernels?
Excuse me if it's a bit of a dumb question..
It has been done but it is not working for 100%. According to droid-developers.org/wiki/2ndboot the GSM part won't work and the last commit at bitbucket.org/droiddev/2ndboot/overview is 8 months ago ...
Related
OK so I have been using the Droid since it's release and been rooted and ran just about every rom and kernel combo there is. I have an eris which is also rooted. I got the X the first day and like all been playing with the rumors of "is root a possibility" and if so are we talking like 12 months for it? I hear the boot loader is locked just like the milestone, do to encryption. I look around and the milestone is rooted already. So what exactly am I missing here for rooting only the new X, just trying to bypass the eFuse with a valid signature?
I mainly want root to remove moto blur and other non-useful apps "imho", although, CM6 with an hdmi driver for 3rd party apps would be nice as well.
So what should I be researching for rooting the X besides, when the milestone gets root so will we approach?
thanks,
shaun
slseale said:
OK so I have been using the Droid since it's release and been rooted and ran just about every rom and kernel combo there is. I have an eris which is also rooted. I got the X the first day and like all been playing with the rumors of "is root a possibility" and if so are we talking like 12 months for it? I hear the boot loader is locked just like the milestone, do to encryption. I look around and the milestone is rooted already. So what exactly am I missing here for rooting only the new X, just trying to bypass the eFuse with a valid signature?
I mainly want root to remove moto blur and other non-useful apps "imho", although, CM6 with an hdmi driver for 3rd party apps would be nice as well.
So what should I be researching for rooting the X besides, when the milestone gets root so will we approach?
thanks,
shaun
Click to expand...
Click to collapse
From what I've been reading is you can't hack the kernal. You can add kernel modules but you can't hack the actual kernel. That means you can't use roms that are not based off that kernal, you can't optimize the kernel, and other things that most custom roms fix. So no Froyo until Motorola releases it and no changing settings that have already been made.
Hi everyone, i am just curious here since everyone said that phone with a locked bootloader is unable to flash a custom rom. But what does it means actually? aren't there are all the custom rom around for our motorola milestone?
From my understanding so far(please correct me if i am wrong, i am a very new to android), locked bootloader means that we can only used a sbf files that are signed officially by motorola only? how they actually made a latest version of gingerbread to milestone? there are tons of question mark in my head i hope someone will be kind enough to clarify to this newbie. Thanks alot.
No one who can provide an answer?
I'm currently thinking about, flashing Cyanogen 7 on my Milestone. However I would like to understand, how it works to run a Rom on a signed boot loader.
Resp. what the drawbacks are (longer boot time?).
Thanks in advance to anyone who can shed a bit of light on this topic.
234m said:
No one who can provide an answer?
I'm currently thinking about, flashing Cyanogen 7 on my Milestone. However I would like to understand, how it works to run a Rom on a signed boot loader.
Resp. what the drawbacks are (longer boot time?).
Thanks in advance to anyone who can shed a bit of light on this topic.
Click to expand...
Click to collapse
Basically what this is, is almost like a Froyo ROM that is running on the least amount of Froyo available (to bypass the signature verification of Motorola's locked bootloader). So even though the kernel shows that it's 2.3.7, it is based off of a Motorola kernel and exploited to port Gingerbread onto the Milestone.
If the bootloader was really unlocked, we would be able to change the kernel, which could improve optimizations for the phone, the CPU, etc. and it has true overclocking of the CPU.
Thanks skadude66, for your explanation
skadude66 said:
So even though the kernel shows that it's 2.3.7, it is based off of a Motorola kernel and exploited to port Gingerbread onto the Milestone.
Click to expand...
Click to collapse
So it is like turning a Dodge Neon into a Dodge Caliber just by changing it's chassis and leaving the engine?
Is the boot time of the exploited kernel longer than the vanilla version?
234m said:
Thanks skadude66, for your explanation
So it is like turning a Dodge Neon into a Dodge Caliber just by changing it's chassis and leaving the engine?
Is the boot time of the exploited kernel longer than the vanilla version?
Click to expand...
Click to collapse
What do you mean by vanilla version? Comparing 2.3.7 to the stock Motorola 2.2.1 kernel in terms of boot times?
skadude66 said:
What do you mean by vanilla version? Comparing 2.3.7 to the stock Motorola 2.2.1 kernel in terms of boot times?
Click to expand...
Click to collapse
Yes, that's what I mean. I imagine this system somehow like an "Virtual Machine", where you have to boot the "host" (2.2.1) before you can boot the "guest" (2.3.7).
Is it like this?
I read the touchpad shares the same exact chip set as the exhilarate. Will I be able to port say, cm9? I'm new to development and porting so any details and help would be appreciated and there is currently no dedicated form for this phone, yet
Sent from my MB860 using Tapatalk 2
It sounds like you intend to port a Touchpad ROM to this phone? I wouldn't suggest doing that, as there are many phones that have the same chipset as the Touchpad, such as the T989. However, the thing with porting is that you are always using the Kernel from YOUR device, not the one you are porting from. This limitation means that you can only port from an existing level of development. Take for example, if you are currently on 2.3.3, you will be limited to porting CM7 ROM's.
I would not suggest flashing a Kernel from another device on your phone unless you are 100% sure it will work. Even with the same chipset, I think some things in the Kernel are executed differently in different devices.
Let me use the Touchpad as an example. I consider it a great device for playing around with because you have Moboot as a protective layer to ensure you do not brick anything. You can flash whatever Kernel you like and it should not brick, but will certainly not work! I flashed a Kernel from my T989 on to it, and all you get is a black screen when trying to boot. Same chipset, different Kernel execution... see my point?
If you were to do that with your phone you would mess up your boot partition and get a hard brick!
Edit: I seen that you found the Forum in Android General about pushing CWM to the phone, that's a good stepping stone!
If you wanted to be brave, I would try pushing CWM from the Blaze 4G, and then Flash one of those ROM's with your Kernel and Radio.
Very informative thanks man!
Sent from my MB860 using Tapatalk 2
First post, but not new to flashing and roms. I have a rooted stock Droid 3 X862 and I'm aware of it not having the two-way calling kernel patch. After an hour of searching, I came upon the bKernel for the Motorola Triumph http://forum.xda-developers.com/showthread.php?t=1322982. I figured I could try flashing that kernel on my Droid 3, but since it's for the Triumph, I didn't know if it would cause any mishaps. Is the flashing of another phone model's Kernel possible and is it wise to do so?
its not possible bue to locked bootloader
You might ask if Hash knows how to use Kexec to use a custom kernel.
Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think
hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!
Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.
So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.