Welcome
|
You have to register before you can post on our site.
|
|
[REQUEST] ASUS TUF Gaming FX505DU BIOS Unlock
|
Posts: 24
Threads: 1
Joined: Jan 2017
Reputation:
0
06-30-2019, 02:06 AM
(This post was last modified: 06-30-2019, 02:10 AM by Tomonok.)
Its AMDs name for VT-x. And the gpu I wanted to switch between the integrated Vega and Nvidia as default output for the BIOS. Its because the diplay panel is connected to the Vega and the HDMI port is directly connected to the Nvidia.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Ohh yes, sorry, we discussed that earlier here Are you on the latest BIOS version? If not, try flashing latest BIOS version and try again, sounds like a bug or something maybe, it should be working even vayana discussed using it previously once he found. Send him and PM and ask him to stop back in here and comment about this, maybe he ran into issue and found a fix?
As mentioned normally you cannot switch display options like that, but since you have programmer you can safely recover if you end up with blak screen.
Please send me a backup of your current BIOS using the programmer, that will be easiest and quickest way for you to put back in mod BIOS anyway.
Posts: 24
Threads: 1
Joined: Jan 2017
Reputation:
0
Yes, i am currently on the latest version (305), but i am right now on a vacation and will get home probably on sunday, so until then no programmer
Once i get home i will make the backup.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
OK, no rush, once you are ready we will get it done
Posts: 24
Threads: 1
Joined: Jan 2017
Reputation:
0
07-08-2019, 01:42 AM
(This post was last modified: 07-12-2019, 05:06 AM by Tomonok.)
So i got home and successfully made the dump. I would be glad if yo could have a look at it. The main things i am interested in:
- the broken svm (i dont know if it is fixable)
- default gpu switch (the HDMI port is directly conncted to the nvidia gpu)
- change memory allocation of the igpu (right now it is on 128m)
- csm mode
- cpu undervolt or some other cpu tdp settings (ryzen master says unsupported cpu)
Thank you very much in advance
Posts: 24
Threads: 1
Joined: Jan 2017
Reputation:
0
07-12-2019, 01:55 AM
(This post was last modified: 07-12-2019, 08:59 AM by Tomonok.)
I have got some good news: Today i installed the latest radeon drivers (19.7.1) and then tried to enable the svm and it worked
EDIT: Okay, so the news are not as good as i thought. It only works without hyperv enabled, otherwise it still ends up in a black screen during boot.
Posts: 24
Threads: 1
Joined: Jan 2017
Reputation:
0
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Sorry, always behind over here
Broken SVM, what do you mean? I see you got it working, somewhat Black screen means incorrect graphics enabled or loaded etc, you'll be able to play around with that once I unlock BIOS for you. Be ready for many recoveries as you test, and be careful to not program in the stock BIOS with your programmer, always use your confirmed working initial backup as your recovery BIOS, or a confirmed working unlocked BIOS made from said backup.
The file above has a few errors, more than the stock one, but that may be normal. What software version did you use to make it, and what is your BIOS chip ID? Did you erase, blank check, and write/verify this back to chip to confirm it's proper yet? If not, don't try yet, wait until you answer the above for me in case I want you to make another using different version for comparison.
Posts: 24
Threads: 1
Joined: Jan 2017
Reputation:
0
With broken svm i meant that black screen. I managed to get it working with vmware, but not hyperv. (so it is not that big of a deal now ).
To the software i used the asprogrammer 1.4 and the chip in this laptop is MXIC MX25U12835F
And the test you mentioned i tried erasing the chip and programming it with the dump i sent you and the laptop works normally (have been using it with it since then), so i think its ok
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Sounds good then, thanks! I will mod this BIOS since you programmed back in the dump and it was OK.
This is unusual BIOS layout, at least the parts that control what's visible/hidden, so it may take several tests of single things, and or multiple bricked recoveries until we reach a final BIOS. Be ready
|
Users browsing this thread: 2 Guest(s)
|