Aspire VX - no bootable device

numzie
numzie Member Posts: 14

Tinkerer

edited September 2023 in 2019 Archives
I had some issues that my screen would not come on after turning of in hibernate/standby (keyboar and the rest running well), so I decided to update to BIOS 1.08.

I downloaded and extracted the official file, ran the .exe and the computer rebooted and seemed to install the new BIOS.

In the very bottom it said something like START EC UPDATE.

Then my machine powered off - rebooted after a while with a No bootable device-sign.

I googled and found out I could enter BIOS, re-enable the F12 and change to Legacy BIOS setting.

Now, this worked and I can get back up again - but...

1. Startup now takes longer
2. It seems like it DID update to 1.08

So... how do I get back to booting UEFI mode again - and what do I do to update the BIOS correct to the new version to see if this fixes my 'screen won't come alive' problem?

Answers

  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    edited August 2019
    If this is the VX5-591G, the BIOS must be in UEFI mode or the GPT-partitioned HDD won't be recognized  as a boot drive.  You probably have to set  and save a supervisor password. Then re-enter the BIOS with the password to change it. Jack E/NJ

    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    Hi JackE

    Thanks. I just need to be VERY sure about which steps to do:

    1. Go into BIOS
    2. Set a supervisor password and SAVE
    3. Re-enter BIOS with password
    4. Change what to what?

    Below pictures of current BIOS settings


  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    >>>4. Change what to what?>>>

    You asked earlier >>>So... how do I get back to booting UEFI mode again >>>

    This is how you get back to UEFI mode if you're having difficulty changing from Legacy mode. Jack E/NJ



    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    Ah yes.

    But going back to UEFI makes the computer unable to boot again.

    My question was - how to fix the BIOS so I can actually boot again using UEFI
  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    Other than the BIOS update, this also suggests that Windows or another operating system might've been re-installed in Legacy mode. How do you think this could've happened? Jack E/NJ

    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    No clue. The only thing I did (seriuosly) was to update the BIOS - and then the problem showed :(
  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    You said earlier>>>I >>>change to Legacy BIOS>>>Now, this worked and I can get back up again - but...1. Startup now takes longer2. It seems like it DID update to 1.08>>>>


    Exactly what are you getting back up again in Legacy mode? Jack E/NJ

    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    Everything looks the same as in UEFI mode - I can't spot any difference. Only thing is the boot takes longer in Legacy-mode.
  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    edited August 2019
    Press Win+R. Enter 'cmd'. At the command prompt 'C : \~~\> ' prompt enter 'diskpart ' . At the DISKPART> prompt enter 'list disk '. There should be about 6 headings labelled Disk ### Status Size Free Dyn GPT. What is listed under each heading? A screenshot would be good. Jack E/NJ

    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    Hm - not much to see.


  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    Enter 'exit' to quit diskpart. At the command prompt, enter 'cd \windows\system32' . At the c : \windows\system32 > prompt enter ' dir mbr2gpt.exe '
    Is mbr2gpt.exe listed? Jack E/NJ

    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    There it is.


  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    OK. At the command prompt, enter 'mbr2gpt /convert /disk: 0  /allowfullos '. After completing, your HDD shouldn't boot in legacy mode anymore. Hopefully, it will  in UEFI mode. I will keep my fingers crossed for you. You should really back up any really important personal files onto a USB stick before doing this. This issue should never have arisen from a BIOS update but once again demonstrates the risks on why firmware updates should only be used as a last resort to try to fix a major problem. Jack E/NJ

    Jack E/NJ

  • numzie
    numzie Member Posts: 14

    Tinkerer

    Thanks. I'll just consider if I want to go into the operation you suggest if it means a possible meltdown, as I don't want to risk that.

    But thanks a lot for your patience and your suggestion!
  • JackE
    JackE ACE Posts: 44,858 Trailblazer
    BIOS updates usually carry a much higher risk of bricking or serious side effects than device driver updates. Your BIOS update resulted in a very serious side effect. In fact, It's the first time I've seen a BIOS update result in a partition change like this without apparently corrupting the file system. Jack E/NJ   

    Jack E/NJ