1. You want that $100.00 in your pocket or an Amazon Fire TV don't you? Well here's the deal. With our new updated look we are in desperate need of an updated logo. The 'old' one has certainly served us well, but it's time. Find all the details here: bit.ly/1q0k6Wa
  2. DroidForums.net is currently undergoing a major software upgrade. If you are experiencing any problems logging in please: Contact Us

can someone explain this to me in some detail? bootloader question

Discussion in 'Motorola Droid 2 Development' started by evilsock, Sep 9, 2010.

  1. evilsock
    Offline

    evilsock New Member

    Joined:
    Nov 12, 2009
    Messages:
    617
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    knox county TN
    id like to think im pretty savvy with android, hacking , dev stuff. but i am lost on this whole bootloader thing.
    how can we have root access, and not be able to swap out a kernal?
    i cant find anything that looks like a kernal on any of my explorations through this phone. yet on my droid 1 its so much different.
    can someone please break down the bootloader and how it differs from the d1.
    maybe even tell me if there is anything else hiding where the kernal is.
    thanks a bunch
  2. mx371
    Offline

    mx371 New Member

    Joined:
    Apr 29, 2010
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    0
    From my understanding, the bootloader checks to make sure that the files being installed on the X are legit from Google, and if not it wont install them. Can anyone confirm/elaborate a bit?
  3. evilsock
    Offline

    evilsock New Member

    Joined:
    Nov 12, 2009
    Messages:
    617
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    knox county TN
    theres ways to trick it, but i cant even find the kernal at all
  4. Eschy
    Offline

    Eschy New Member

    Joined:
    Jun 4, 2010
    Messages:
    218
    Likes Received:
    0
    Trophy Points:
    0
    we cant access the boot.img yet, this is where the kernel is located. None of the system dumps have it because it is separate from the /system files. If you look at a zip file from a custom rom they have the boot.img in there but because the bootloader is locked there is no access to this file. Correct me if im wrong but this is what i have gathered from this whole thing.
  5. ultima
    Offline

    ultima New Member

    Joined:
    Jul 3, 2010
    Messages:
    122
    Likes Received:
    0
    Trophy Points:
    0
    im a little lost on this too...is kernel flashing the only thing D1 does that D2 cant?
  6. Redflea
    Offline

    Redflea New Member

    Joined:
    Nov 18, 2009
    Messages:
    1,954
    Likes Received:
    3
    Trophy Points:
    0
    That's correct...we have root and custom recovery, but no kernel access yet.

    All we can't do is flash a custom kernel to allow overclocking. Given we have a 1GHz CPU, not a biggie for me.... :)
  7. czerdrill
    Offline

    czerdrill New Member

    Joined:
    Jan 2, 2010
    Messages:
    4,828
    Likes Received:
    12
    Trophy Points:
    0
    Not exactly. With a locked bootloader you are limited to whatever kernel motorola wants to give you. So if verizon decides to end support for the x and motorola releases no new kernels development for the x ends. In other words If motorola doesn't release a gingerbread kernel for example you're stuck on froyo forever. The d1 you can put gingerbread on regardless of whether motorola releases it or not by building it from source. So right now it may not matter but the x won't have a great a shelf life as say the g1 which is still being developed for.

    Also it'll suck waiting for motorola to release gingerbread when d1 owners will be running it months in advance kind of like how you have to wait for froyo right now if you didn't install the leak (also from motorola).

    Locked bootloaders suck is the underlying theme lol