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.
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.
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 got a early upgrade today and i am wondering what development has gone on. i know it has recovery mode and i know that you can put roms on it. but does it have a asop rom? also is the rom fully unlocked or is it like how the droid x used to be? thanks any help will be great because i dont know if i want to wait for the galaxy prime(nexus prime/droidprime) or get this already.
I've deodex my phone so far.
Sent from my DROID BIONIC using Tapatalk
The bootloader is locked like the DX there are people working on finding the unlock procedure for it but there will be no ETA on that (if ever) until it happens. Honestly if you are concerned with Modding, considering the amount of attention this phone has already received from the Dev community it should be a heavily developed phone. It has been out for just over 10days and already rooted, strapped, and CM7 under development. However remember the phone does have a locked bootloader so that means no kernel flashing, which sucks but, considering I don't feel the need to overclock just yet and my battery life if wonderful, I just don't see the need for a new kernel yet.
--
I have looked and I may have missed it, but I was wanting to know for certain if miui or cm roms can install on stock rooted 2.2.2 frg83 droid 1/og. I have miui on my x and my husband FINALLY let me get my hands on his (my old) droid. I can not find any where that lists the system requirements. I really dont want him to see me have to sbf his phone or anything... that may make him think I killed it. it has cwm, titanium backup and rom manager pro.. any link to a list of roms I can use would be great I am sorry if I over looked this somewhere. It seems the droid 1 has been left in the dust.
Thanks in advance
Hi All,
My Moto X (1st Gen) is about 4 months old. I'm contemplating on rooting the phone. Is it worth the effort or should I patiently wait for the Lollipop update to come in (whenever that is!). I used a lot of custom roms in my old Nexus 4, so missing the excitement of a new rom. just a bit indecisive at the moment. Would love your opinions on this.
arjun2058 said:
Hi All,
My Moto X (1st Gen) is about 4 months old. I'm contemplating on rooting the phone. Is it worth the effort or should I patiently wait for the Lollipop update to come in (whenever that is!). I used a lot of custom roms in my old Nexus 4, so missing the excitement of a new rom. just a bit indecisive at the moment. Would love your opinions on this.
Click to expand...
Click to collapse
I am using the Moto X for nealry 9 months now. Never thought of rooting it as I didnt find any bloat here like the Touchwiz
I am honestly very tempted by the ROMs out there. And I don't know why but I'm definitely noticing some performance lag. Tried everything but not seeing a lot of improvement.
Sent from my Moto X using XDA Free mobile app
Before you go contemplating this question, figure out if you'll be able to root your phone in the first place.
Then instead of asking this question, ask whether or not you should unlock the bootloader. It's the only way to maintain root since 4.4.4 patched the vulnerabilities used to attain root.
There are reasons why I would root like Tasker(full functionality),a custom kernel or UI changes
I rooted my X so I can play with gravity box and other stuff. Unrooting and relocking the bootloader isn't hard to do and that's what I'll do once Lollipop comes out for my phone. (Already factory reset my phone once from custom Rom).
TheBoiledDogs said:
I rooted my X so I can play with gravity box and other stuff. Unrooting and relocking the bootloader isn't hard to do and that's what I'll do once Lollipop comes out for my phone. (Already factory reset my phone once from custom Rom).
Click to expand...
Click to collapse
You are going to re lock your bootloader to take Lollipop?
Travisdroidx2 said:
You are going to re lock your bootloader to take Lollipop?
Click to expand...
Click to collapse
I meant to say return to stock recovery. I read somewhere that you can't get OTA with a custom recovery, Rom and rooted.
TheBoiledDogs said:
I meant to say return to stock recovery. I read somewhere that you can't get OTA with a custom recovery, Rom and rooted.
Click to expand...
Click to collapse
Gotcha, that is true. Stock recovery and stock system and you are good to go.
I personally root all my devices for better control. However, I personally don't use Roms because I want a stock experience and that includes boot animation and themes. The only Roms I have ever kept on my phones were ARHD and Paranoid Android. If neither are available, I go with Xposed.