ASUS ROG GL702VM Stuck at ROG logo after bios update

Discussion in 'Asus' started by vesayreve, Sep 10, 2019 at 10:04 PM.

  1. vesayreve

    vesayreve Notebook Evangelist

    Reputations:
    0
    Messages:
    316
    Likes Received:
    41
    Trophy Points:
    41
    Hello guys,

    I was having an issue with my laptop after the recent windows update. Keyboard would stop working randomly then closing and opening the lid would solve it. So I wanted to fix it permanently, checkted the bios site and wow there is a new bios OK lets try. Stupid me....

    Flashed the new bios with the asus easy flash tool. It seemed it went fine. Pc restarted then bam its forever stuck on asus rog logo.

    However, the blame could be on MS. My boot is on m.2 ssd. When I remove the ssd I can access to bios but with ssd it just doesnt load and i cant even access bios like that.

    Please I have important documents that I need to submit this friday. Save me...
     
  2. vesayreve

    vesayreve Notebook Evangelist

    Reputations:
    0
    Messages:
    316
    Likes Received:
    41
    Trophy Points:
    41
    Also, if it matters after the stupid MS update my wallpaper went black for some reason. Didnt think much about it.

    I am using windows 10 out of box(It was home edition)

    Ssd that windows is installed on is samsung m.2 500GB.

    I tried removing the ssd from pcie and putting it to sata, doesnt work.

    Model is gl702vt which is the same as gl702vm but with 970m instead of 1060.
     
  3. vesayreve

    vesayreve Notebook Evangelist

    Reputations:
    0
    Messages:
    316
    Likes Received:
    41
    Trophy Points:
    41
  4. vesayreve

    vesayreve Notebook Evangelist

    Reputations:
    0
    Messages:
    316
    Likes Received:
    41
    Trophy Points:
    41
    Just realized title is GL702VM. How can I fix that? I have GL702VT.
     
  5. vesayreve

    vesayreve Notebook Evangelist

    Reputations:
    0
    Messages:
    316
    Likes Received:
    41
    Trophy Points:
    41
    I fixed this by downgrading to the previous bios. Unacceptable mistake on asus' part
     
Loading...

Share This Page