DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Getting Custom Kernels Running on the Droid X
- Thread starter aliasxerog
- Start date
No posts since Gingerbread has been leaked and rooted...
:unsure:
This sucks. Really. It blows. Even though my Rooted Gingerbread is smooth as silk... it blows.
I'm really hoping that something happens.
I know nothing about writing code, or anything developer-wise. I've barely been with Android for almost a year. Rooting and ROMing are about the extent of my knowledge.
But from what I've just read here on these forums and whatnot.... this is what I've gathered.
There has to be some way to hack the hardware of the phone to find out the information needed to crack the bootloader. If all the drivers are signed, and the HARDWARE (the phone itself) looks for that signature, then isn't there some way of getting into that hardware, and rewriting the programming stored in the hardware to where it doesn't even bother to look for a signature/key, therefore making it to where we can but any bootloader we want on, and therefore making the whole phone unlocked?
It's just an idea. Like I said, I really have no clue what I'm talking about at all. I'm just reading and thinking.
:unsure:
This sucks. Really. It blows. Even though my Rooted Gingerbread is smooth as silk... it blows.
I'm really hoping that something happens.
I know nothing about writing code, or anything developer-wise. I've barely been with Android for almost a year. Rooting and ROMing are about the extent of my knowledge.
But from what I've just read here on these forums and whatnot.... this is what I've gathered.
There has to be some way to hack the hardware of the phone to find out the information needed to crack the bootloader. If all the drivers are signed, and the HARDWARE (the phone itself) looks for that signature, then isn't there some way of getting into that hardware, and rewriting the programming stored in the hardware to where it doesn't even bother to look for a signature/key, therefore making it to where we can but any bootloader we want on, and therefore making the whole phone unlocked?
It's just an idea. Like I said, I really have no clue what I'm talking about at all. I'm just reading and thinking.
furbearingmammal
Super Moderator
Even with the signing keys it's impossible to fake a signature.
The only way this puppy is getting hacked is after many, many computer-years of effort in a brute-force attack. The only way that'll happen in our lifetimes is if it's a distrubuted-model, similar to the BOINC project, and even then it's iffy. However, if the bypass works on GB then there's a very good chance we'll have truly custom kernels running eventualy.
The only way this puppy is getting hacked is after many, many computer-years of effort in a brute-force attack. The only way that'll happen in our lifetimes is if it's a distrubuted-model, similar to the BOINC project, and even then it's iffy. However, if the bypass works on GB then there's a very good chance we'll have truly custom kernels running eventualy.
There's a bootloader bypass? If so please explain.
My X will be here in a couple of days, then my kexec adventure begins...if it can be done on the Sony Xperia surely it can be done on the X.
Go around the bootloader, it is the only way...or Motorola feeling generous after EOL.
They bypassed it on the X10 basically using what your trying to do. There's an article over on XDA about it.
sent from a D2G with Liberty 2
Last edited:
furbearingmammal
Super Moderator
What they said. 
Ill get a hold of this guy and see what he did. Any contact info? I really didn't see any in the thread
Sent from my Droid X running AOSP and linux kernel 2.6.38.
Sent from my Droid X running AOSP and linux kernel 2.6.38.
Can you send him a PM.
From what I'm getting from this is the X10 has a different hardware arch than us, hence is easier to use kexec on. It even looks like they're using my driver patch on it (could be convergent evolution though).
Sent from my Droid X running AOSP and linux kernel 2.6.38.
Sent from my Droid X running AOSP and linux kernel 2.6.38.
What makes you think a different arch is any easier to work with?
