does ODIN by secr9tos work for UEFI Win7

Discussion in 'Windows 7' started by imgwhirl, Mar 27, 2015.

  1. imgwhirl

    imgwhirl MDL Novice

    Jul 13, 2014
    49
    10
    0
    #1 imgwhirl, Mar 27, 2015
    Last edited: Mar 27, 2015
    for sake of this, let's exclude any private odin release from the discussion, & instead focus on technical details.

    i know odin patches kernel to load its unsigned driver which may be undesirable, but what if i am well aware of the consequence and still decide to proceed? does it work on UEFI install? coz it was advertised as hardware independent.
    if not, can anyone share its working principle as to why it is restricted to BIOS MBR install?

    *i ask this for learning purpose, please avoid solely suggesting other activation methods as a reply.

    EDIT: We know that Daz's Windows Loader works by modifying MBR to inject SLIC so it requires MBR harddisk partition. So it won't work in UEFI Windows with GPT partition.
    What I wonder is, if ODIN changes SLIC cached in RAM through boot-start driver, shouldn't it work on UEFI too? as it probably had made no assumption on underlying harddisk partition. or does the SLIC structure or position differs from BIOS to UEFI, such that the tool must be redesigned?
     
  2. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,171
    10,928
    340
    #2 Yen, Mar 27, 2015
    Last edited: Mar 27, 2015
    As posted already support has been cancelled for ODIN a long time ago at MDL since the author moved the project away from MDL and made it to an paid activator (paid VIP access for D/L).

    On AMD64 operation systems ODIN patched ntoskrnl and winload to remove "Driver Signature Enforcement" & "PatchGuard". All other modifications (get a SLIC) are done in RAM ( AMD64 & x86 )
    The tool installed a driver named oem-drv86.sys or oem-drv64.sys.
    AFAIK it did not run on I386 with PAE / Itanium64.
    To me it is unknown if it works with MBR only and why....one would need to know how the SLIC is introduced into ACPI namespace (EBDA for relocation of RSDP might not work/be available at GPT boot?)
    Is it an EBDA approach?


    I let this thread run for tech discussions.
    If one of the MDL member can help with info feel free to reply.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,171
    10,928
    340
    Actually grub bootloader used in Daz loader requires a MBR to be called, it has nothing to do with the SLIC introduction method itself.
    Bootchain: BIOS-->MBR---->grub loader with SLIC introduction code--->bootsector/bootmgr --->OS/OSes...
    w/o loader: BIOS-->MBR--->bootsector/bootmgr--->OS/OSes

    Btw: Why don't you try yourself if ODIN requires MBR or not?!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,574
    15,382
    340
    AFAIK, ODIN is succeed by ĀµODIN & the last 'leaked' version is 1.0.0.2.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,171
    10,928
    340
    They suck either way, lol.
    I'd go for WindSLIC or even better an UEFI mod when using GPT installations which activate against a SLIC.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Mr.X

    Mr.X MDL Guru

    Jul 14, 2013
    5,854
    13,388
    180
    I agree Yen, it sucks. Any version of the activator.
    Btw, according to his author the latest version is uODIN-R2 never tested by me (right after 1.0.0.2) but is no longer supported by him/her.

    FAQs:
    Requirements for Server 2008 R2:
    .NET Framework 3.5.1 Feature


    Generate Report feature - Privacy:
    The data included in the report does not contain private information in any way.

    Included in the generated package is:
    * HKLM\HARDWARE
    * HKLM\SYSTEM\CurrentControlSet
    * %systemroot%\Minidump\*.dmp
    * %systemroot%\System32\drivers\uodin.sys
    * MGADiag log
    * uODIN-R2 log(s)


    Does uODIN-R2 store files on my PC?:
    Yes, application logs and old reports are saved to %localappdata%\uODIN-R2.


    Can I upgrade from uODIN 1.0.0.2 to this release?:
    No, you need to uninstall the previous release first before applying this one.




    Do I really need to restart between un/install?:
    Yes, as otherwise your PC might stay in test-mode after a complete uninstall.


    In case you encounter a BSOD
    1. Boot into recovery console and type:
    del <volume_label>:\Windows\system32\drivers\uodin.sys
    2. Reboot
    3. Launch uODIN-R2 and uninstall all remaining components

    In case you encounter any problems
    Sorry, no longer supported by the author.
     
  7. Mr.X

    Mr.X MDL Guru

    Jul 14, 2013
    5,854
    13,388
    180
    I don't like the "In case you encounter a BSOD" part. secr9tos is assuming that tampering with system files and drivers is a messy thing.