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?
Related
This was the tweet fromCvpcs!!! (We haz a booting "true" AOSP system with 0 blur! http://www.youtube.com/watch?v=PPqfIRZP7Mc Still very buggy but I'm working on it)
Sent from my DROIDX using XDA App
booyah! let get er done!
Sound like good news!
Still, could anybody explain what AOSP boot means? Will this enable us to boot a custom kernel on the x?
I have no idea what this means except 100% no blur sounds awesome!
AOSP essentially means it was built completely from source. Not built based on Moto's own build with their custom framework (blur) crap. It is a true complete Vanilla rom.
Android Open Source Project
http://source.android.com/
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
If they got an aosp to run they should be able to modify the kernel no? Thought that was the while point of the exploit nenolod is working on.
Sent from my DROIDX using Tapatalk
this is too awesome.
Joe92T said:
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
vonfeldt7 said:
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
This AOSP has actually been running for a while now. Its being developed by cvpcs, the same guy who's been developing the Sapphire roms for Droid. I don't know if he's using the recent exploit that has made the rumor-mill lately. He claims its a true AOSP boot, which implies a custom kernel compiled from source. However, for all we know he could still be using the Moto 2.2 kernel, but replaced everything else in user space with fresh, compiled code.
Either way, its interesting. Despite Motorola's best attempts, it looks like the Droid X (and Droid 2 by implication) will soon be free of its eFuse prison, allowing us users the choice of what to run on this device.
We won't be getting rid of eFuse, as it's hard coded into the silicon itself in NVRAM, as I understand it. Its just that folks are working on getting the keys to the prison .
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
sniffle said:
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
Click to expand...
Click to collapse
Thank you guys for your hard work, I am sure that most of the community is as excited as I am to see your work make it to the X. I love the boot ani from the video, and even though this is my first android phone the things Ive read about your teams previous releases has me EXCITED for this to hit.
appreciate your update and clarification, sniffle!
OMG, aosp 2.2 for my droidx would be awesome. Nice to set someone working on it, props and kudoes.
Sent from my PC36100 using XDA App
i hear this is almost 100% working!
LT1UltraZ said:
i hear this is almost 100% working!
Click to expand...
Click to collapse
Heard the same this morning. Very excited!
dogswind said:
Heard the same this morning. Very excited!
Click to expand...
Click to collapse
Would love a source on this info.
Almost 100% is a bit too strong of a descriptor, there are still some major bugs like rebooting on sleep(hitting the power button to turn the screen off) and a few others on top of that. With our next sapphire and Ruby release we will be making the latest build publicly available for other development to help figure out a fix for these problems.
So a thought that has occurred to me since I got this phone is one of haret.exe on winmo phones. basically boot up past the bootloader and kernel(that are locked) then using either 2ndboot or kexec dump out of that kernel and launch out own kernel/filesystem
Sadly in looking around 2ndboot seems to require the phones kernel source(which we don't have, unless i'm totally wrong)
kexec on the other hand seems to be a much better way to accomplish it. Again this is mostly useless without a kernel BUT we could take our current kernel to use as a test bed for if (as is required) the release the kernel source.
Thoughts? anyone wanna join with me on trying to get this running and tested?
art3mis-nyc said:
So a thought that has occurred to me since I got this phone is one of haret.exe on winmo phones. basically boot up past the bootloader and kernel(that are locked) then using either 2ndboot or kexec dump out of that kernel and launch out own kernel/filesystem
Sadly in looking around 2ndboot seems to require the phones kernel source(which we don't have, unless i'm totally wrong)
kexec on the other hand seems to be a much better way to accomplish it. Again this is mostly useless without a kernel BUT we could take our current kernel to use as a test bed for if (as is required) the release the kernel source.
Thoughts? anyone wanna join with me on trying to get this running and tested?
Click to expand...
Click to collapse
I believe this was discussed already in the thread about cracking the bootloader, however, if you do manage to get this running I will gladly beta a new kernel as long as there is an SBF file available at the time to allow flashing back to stock.
Cheers
Ill gladly beta as well. So long as we have a method for recovery.
Sent from my MB860 using XDA App
Hi all develoers here. Salute to you all for whatever you did for our milestone.
Just a noob question. Is by any chance, by stripping down, or by any magic, is there a possibility to port Android 3.0 for Milestone? Is it possible?
http://developer.android.com already released information and sdk about 3.0. Any expert comments about hardware requirement or any hardware comparisaon details available yet?
I have seen many chinese android tablets and devices with same or lower configuration than milestone running with higher versions like 2.3.3 and some even claiming to have 3.0. (There are already many 3.0 tablets on ebay with lower configuration than Milestone. http://cgi.ebay.in/BRAND-NEW-8GB-7-...31243148?pt=IN_PC_Laptops&hash=item4cf532848c )
Any possible luck? Any experts there?
The old HTC G1 even can run 3.0 (just for fun, nothing more) so i think MS can run 3.0 (but...just for fun, nothing more...^_^).
As sayd, maybe MM can run 3.0 with some hack/tweak/mods, but nothing farther...
Google says that 3.0 is for tablets intended, 2.3/2.4 and so on for mobile
MM can't run Honeycomb, cause we have locked bootloader.
I can't imagine Honeycomb with Froyo kernel
keunhuvac said:
The old HTC G1 even can run 3.0 (just for fun, nothing more) so i think MS can run 3.0 (but...just for fun, nothing more...^_^).
Click to expand...
Click to collapse
Then why not for fun? When other low-configured devices can run 3.0 seriously, then why not on Milestone, which actually have good confi?
lvcio said:
As sayd, maybe MM can run 3.0 with some hack/tweak/mods, but nothing farther...
Google says that 3.0 is for tablets intended, 2.3/2.4 and so on for mobile
Click to expand...
Click to collapse
Do you still believe that developers should stick to what google or anyone else said? Most of the new tablets runnung 3.0 have similar configurations and even resolution of milestone.
ovitz said:
MM can't run Honeycomb, cause we have locked bootloader. I can't imagine Honeycomb with Froyo kernel
Click to expand...
Click to collapse
Do not agree. Milestone is already rooted and thousands of experimets with GB is already done. Seems you dont visit milestone rom developement section. Its always better to get some information before commenting with dead ends.
Anyways thanks all for your inputs.
Are they still trying to Bruteforce open the bootloader? Or did they give up?
It's still open at www.androinc.net, but most of us don't trust the project since the source was never released and it just seems shady.
almost a month over, but no useful information from motorola nor any developers. Seems motorola bootloader will never be cracked in future.
indiacam said:
Do not agree. Milestone is already rooted and thousands of experimets with GB is already done. Seems you dont visit milestone rom developement section. Its always better to get some information before commenting with dead ends.
Anyways thanks all for your inputs.
Click to expand...
Click to collapse
You are wrong. All the latest rom available for MM is over froyo kernel and no GB as you stated. Yes we now run GB on our MM but the Kernel still Froyo. I think YOU should start read the DEV section a bit more instead of saying this things.
Peace
Sent from my Milestone using XDA Premium App
Google has clearly stated that Android 3.0 is only meant for tablet use.
Hi,
I'm using unlocked captivate with T-mobile.
I recently installed galnet MIUI for captivate, with GT-I9000 bootloader.
I was wondering, since i am on GT-I9000 bootloader, wouldn't every single one of stuff on my phone (kernel, moden, etc) should be I9000 version of it, for better performance?
right now i am on baseband version of I9000XXJVK
with i897 version of galnet miui stock kernel.
shouldn't i change my stock kernel to i9000 version of it, since bootloader is i9000?
thx in advance.
no, unless you want your rotation, sound, soft keys, elect messed up.
I897 and I9000 are similar not the same. Something work cross device like modems, and others require porting to work like roms and kernels
speedy_11 said:
no, unless you want your rotation, sound, soft keys, elect messed up.
I897 and I9000 are similar not the same. Something work cross device like modems, and others require porting to work like roms and kernels
Click to expand...
Click to collapse
thanks for the answer.
on more thing tho, what do you mean by requiring porting to work?
dskim0506 said:
one more thing tho, what do you mean by requiring porting to work?
Click to expand...
Click to collapse
Porting means modifying software to work on another platform, which can be either a different operating system, or different hardware. For instance, a software developer might be asked to port his windows program to mac or linux. This usually means rewriting or modifying the source code and then re-compiling the program. (This example would not be trivial, probably requiring almost a complete rewrite, lol.) In the case of I-9000 and I-897, there are some differences in the way the hardware is configured between the two phones, and that requires the software to be configured somewhat differently, mostly in the kernel, which is the software layer that most directly works with the hardware. Once the developer has access to the source code, then he rewrites those sections of code that relate to the hardware differences, and the software is re-compiled. So, software originally written to work with I-9000 hardware can then work correctly with the I-897.
still not working...
tried 3 times, and still not working.
in recovery mode, i wiped cache and dalvik cache, and then flashed talonMTD kernel for captivate
the phone still gets frozen after screen goes off
Thats weird. You did that from a fully functional miui install? I don't see why it would fail.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
T-T
xijar said:
Thats weird. You did that from a fully functional miui install? I don't see why it would fail.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'd say i did everything right.
well, i'm on galnet miui 1.8.12...
i followed this instruction:
http://www.galnetmiui.co.uk/content/forum/guides/(work-in-progress)-lttldvl's-clean-install-method/
doubt this makes any difference, because it didn't work when i flashed regular miui by following
http://miuicaptivate.weebly.com/install.html
after all these, i did format both cache and dalvik, then went to install from zip,
then flashed TalonMTD.
after that, I reboot, install setcpu, undervolt -100 for 1GHz and down,
turn the screen off, and the phone gets frozen after few seconds....
waahhhhhhhhh
Too much UV in the 100 mhz zone
Corrupted TalonMTD download
Does the TalonMTD work on Galnets MIUI?
Sent from my Cappy at 1.6 GHz, V6 supercharger, KAK tweaks, and 3G booster using the XDA Premium App!
Your phone should be on i897 bootloaders. The kernel should be tuned for the hardware (i897) and the bootloades need to be for the hardware as well (i897). The bootloaders are responsible for initializing the hardware and the kernel runs the hardware. Don't change your bootloaders...
Regardless of which Developer says "OMFG HEY RUNZORZ MY ROM CUZ IT'S GOOD" never change your bootloader. Those "Developers" are retarded.
Hi!
I was wondering if it would be possible to run a CM userland on a stock kernel (Yes I am one of those fools who bought a device with "bootloader unlock allowed: no").
This has been done in the past for other phones and apart from delivering a CM experience to locked phones this would also allow for a working Bravia engine on CM. Sure there would be some limitations when running such a setup (e.g. because of certain kernel modules not being available), but Sony seems to update the official firmwares at a acceptable pace, so there are fairly recent official kernels available: Most recent stable CM is based on 4.2.2 as is Sony's most recent firmware.
I can hardly estimate how problematic other aspects (ABI version mismatches, etc..) might be when trying this, but I remember CyanoSpaceMod for the XU which worked for devices with locked bootloaders. It was a working CM9 and implemented CWM in the same manner as the dual recovery on the XZ for locked bootloaders running on the stock kernel.
All in all it seems to me that all the building blocks are there, but I have no experience in building CM, so I cannot do this on my own, I need some guidance.
Would it be enough to simply build CM for the prebuilt stock kernel as outlined here, even if it meant that tehre would be no CWM support initially? The kernel itself can easily be extracted from a stock rom...
Any help -- even just an educated guess -- would be appreciated.
Not possible matey.
DrKrFfXx said:
Not possible matey.
Click to expand...
Click to collapse
Could you point me to somewhere, where I can find an elaboration on the subject so I can educate myself?
Why is the XZ so much different than other Sony phones? Or is it simply because Sony was so forthcoming in open sourcing everything they legally can, fostering kernel hacking so that the CM kernel now differs greatly from the stock kernel?
In that case I can fully understand that major changes in the CM base would be required to make it run on the stock kernel...
(I am actually just asking out of curiosity, since I got an unlockable device yesterday )