• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

BDS Menu on non Prototype devices

Search This thread

DaniDeVega

Member
Jun 23, 2016
35
7
Huelva
Note: currently looking at a problem where the block id for efiesp might differ between phones, if you get an error message saying can't load menu configuration file, please tell me your device model.

Edit: Fixed for some other problematic devices, I'll send an alternative version of the menu to see if it fixes it for most with the two variants


Hi gus! Is it fixed and available now for Lumia 920 (RM-821 model)? I have now Compilation 10.0.15254.490 tweaking registry saying that is a Lumia 950 XL (RM-1085_11302) running well in this moment. If not available or tried yet on a 920, I would like to test it, but first must know how to deploy/implement to my device.



PD.: Adding here a little doubt I have. I'm unsure if I can now update Extras & Info or it could be a problem yet, after updates has finished at this moment. If I relock my bootloader, It doesn't boots on normal anyway, and I usually read that it mustn't be updated while bootlader stays unlocked, but since many time has passed that my last phone tweaking, I don't know if it still getting forbidden or finally not.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this package
    * before installing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    M16kROu.jpg


    You read it right, here's a functional port of BDS Menu for Lumias unlocked using WPInternals.
    Note: I observed some weird behaviors on early x30 devices, including prototypes that had BDS menu out of the box, where the menu would simply act like if it was broken.

    The bootarm.efi loader has been taken from the grub package posted here and modified to load menu.efi instead of boot.efi, credits belong to the original person that developed this efi in 2016.

    Note: attached two variants, a normal one (fs3) and a fs4 variant, if you get an error about the menu not finding its configuration files, please try the other variant.

    Installation instructions:
    • Download the files attached in this post.
    • Place all files downloaded in the EFIESP partition of your phone.
    • Configure BCD exactly like this to have an entry loading BDS menu:
      Nc1XzOP.png
    • Load the entry using your favorite method.
    • Have fun.
    3
    I'll try to work on fixing the "blinking issue" but that's also reproducible on some early prototypes, but should be working definitely on a 950.

    Also here's a fixed bootarm.efi (shim) for 950 XLs that had issues with the original one, replace boot/bds/bootarm.efi with this one. I'll fully update the package later.

    Edit: fixed version
    3
    Note: currently looking at a problem where the block id for efiesp might differ between phones, if you get an error message saying can't load menu configuration file, please tell me your device model.

    Edit: Fixed for some other problematic devices, I'll send an alternative version of the menu to see if it fixes it for most with the two variants
    3
    Could you explain how to configure bcd using bcdedit please?

    like this...
    rmkLjD04p8Y.jpg

    also need add device
    bcdedit /store .\BCD /set "{7e1bd2b8-0ab0-11e8-aa3b-1c3947b79a68}" device partition=f:\efiesp
    and(in my case) add it to customactions( activation by vol up/down )
    bcdedit /store .\BCD /set "{bootmgr}" custom:54000002 "{7e1bd2b8-0ab0-11e8-aa3b-1c3947b79a68}"
    (custom:54000002 == vol down, custom:54000001 == vol up)
    2
    That shim file might not work on 950XL, it simply reboots my phone - haven't figured out why, probably due to new CPU architecture or the firmware itself