Jump to content

elcaballo

Registered User
  • Posts

    16
  • Joined

  • Last visited

Posts posted by elcaballo

  1. So here is where I am at now. I ran backup.bat from a adminstrator Command Prompt but I get the following error.

    [ATTACH=CONFIG]6156[/ATTACH]

    Did you have your anti-virus activated? If it was activated at the time you executed the .exe, you might want to disable your anti-virus before doing the backup. Hope it will help! =)

  2. I have a very serious problem with my wifi network. I have a router ASUS RTn66u, which gives the 2.4 GHz and 5 GHz simultaneously. I have no problems to connect to the router in the 5GHz band, but the 2.4 GHz band can not connect. I have at home a few other devices that use the 2.4 GHz band and I have no problems with their communications. All devices except Y580 connect seamlessly with the router on the 2.4 GHz band. I have unlocked the BIOS version from the first post version 2.06. The problem occurs both with the Intel 6200 and Intel 6300. None of these cards is able to connect to the network at 2.4 GHz. When I tried to connect to the network using 2.4 GHz intel card 2200 (original from Y580) everything was fine. I wonder if any of you have a similar problem. Earlier I do not tried to connect to the 2.4 GHz network so the problem I discovered today. I wonder if there is any chance that it is the fault of the BIOS. I would add that both 6200 and 6300 cards working fine on my second laptop (HP). I will be grateful for any feedback.

    Today I tried to connect to 2,4GHz network using intel 5100 wifi card taken from HP laptop. The card isn't broken - 100% fully operational because it is working 2,4GHz and 5GHz on HP.

    So there is something wrong... have no idea what.

    On page 5 of this thread, somebody had the same problem you are having I think. http://forum.techinferno.com/lenovo-ibm/2260-lenovo-y580-y480-unlocked-bios-versions-5.html

    He posted a modified BIOS. I think the link is dead but somebody re-posted it somewhere in this thread. You could give it a try and see if it solves your problem. Will try tonight my 6300 and will keep you updated if I have the same problem.

    ---EDIT:

    At the end of this page: http://forums.mydigitallife.info/threads/20223-Remove-whitelist-check-add-ID-s-to-break-hardware-restrictions-mod-requests/page321

    Somebody posted the no-whitelist version of the Bios 2.07. The following post indicates that it looks like it is working with the 6300 (it does not say whether it worked with 2.4 and 5 Ghz networks): http://forums.mydigitallife.info/threads/20223-Remove-whitelist-check-add-ID-s-to-break-hardware-restrictions-mod-requests/page322

    ---EDIT 2:

    I just installed the Intel 6300 and I am not having any problem connecting to a 2.4 Ghz. I am on the 8.01 Bios version.

    • Thumbs Up 1
  3. Does it matter which USB port?

    I don't know if it will solve the problem, but maybe try the USB port next to the power plug. I know that when I was using PING (Partimage Is Not Ghost), I had to plug my hard drive in this port for it to be recognized. It could make sense since it is the only USB 2.0 port.

  4. Thank you very much svl7 for the Error 104 fix and the BIOS mod. I didn't flash my BIOS yet, but I was able to back it up with no problem (after disabling my anti-virus) with the fix.

    I will flash my BIOS after the week-end probably and will get you some beers for sure =)

    Good luck with your SSD, I hope Intel will replace it even though it will not bring your data back.

    • Thumbs Up 1
  5. svl7, being part of the "Error 104" group, I am wondering if using a newer version of Intel Flash Programming tool would solve the problem. Maybe it is due to a bug in the Intel tool. What do you think?

    When looking at the Lenovo driver matrix for the Y580 (Drivers and software - IdeaPad Y580 Notebook), it looks like they released the version 8.1.0.1248 of Intel Management Engine Interface. I don't know which version of the flash programming tool is provided though.

    Thanks!

  6. According to this thread on the Lenovo forum, it should work:

    Re: Y580 16GB RAM Support - Lenovo Community

    I don't know if it matters for the BIOS version. When I look at the date the messages have been posted (July - August 2012), these people had "old" BIOS versions since the latest versions were not released yet. In the worst case if it doesn't work, you can always upgrade to the 2.06 (with no whitelist and/or unlocked from svl7) that is on the first post of this thread, or you can even upgrade to the 2.07 (not unlocked and with whitelist) that is on the official Lenovo support web site. If you play games on your laptop, the 2.07 version seems to fix problem with 3D games by the way!

    Edit: this thread confirms it too:

    FOR ANYONE WHO IS CONSIDERING TO UPGRADE Y580 TO 1... - Lenovo Community

  7. * If I installed new WiFi card, BIOS refuse to load Windows - just like I expected,

    BIOS version was 2.07 without any modifications - original LENOVO.

    I turned on Y580 once again, but then immediately pushed F2 and enter to BIOS, changed nothing, and SAVE AND EXIT... I was very surprised but BIOS passed my new WiFi card. Don't checked yet if this card will work under windows but it might. Can YOU do the same???

    Tried it tonight with the BIOS 5DCN90WW and an Intel 6300, but I got the message that the wireless card was not allowed!

  8. @En-TACT, I also have the same BIOS version (5DCN90WW), but my model number is different: 59359513. When I was shopping around on Amazon, New Egg, etc. last week, I noticed that there are a lot of model numbers out there, all with little variations in the equipment of the laptop (SSD or no, Blu-ray or no, HDD size, this kind of difference). I got mine on the Lenovo web site and I was not able to find the same model number anywhere else.

    @darius456 I will try your trick tonight and will see if I can reproduce it with my BIOS version. That would be cool! =)

    Will try with an Intel 6300.

  9. Did you get the drivers from the Intel web site? I assume you are working on Windows. Maybe try to uninstall completely the drivers of the old card first and then install the drivers for the new one. Just in case Windows messes up with the drivers. It might be that it tries to use the drivers for the old card.

    Also, did you try on something else than Windows? Ubuntu or another Linux distribution? You should be able to run Ubuntu via the Live CD you can download on their website without installing anything on your hard drive. It would allow you to check if Windows is guilty in this story or if the compatibility of the system and the card is the one to blame.

  10. Right click each file and go to > General tab > click on Unblock (if available). Then for file fptw64, right click > Compatibility tab > check mark Run as Administrator. Finally, for FLASH right click > select Run as administrator to execute process.

    Thank you for your response =) I am still sticking with the Error 104 though. I guess we cannot do anything about it for now.

    All bios will work with Win8 and Win7, but only the more recent ones (not yet available at Lenovo's site) have the secure boot / fast boot features. It probably also introduced the Win8 activation stuff.

    I'm not sure what I can do about error 104. Error 28 can be solved, but for some reasons it didn't work properly on the system of EN-TACT, so I have find a workaround for my method.

    Thank you for your work svl7. Let's hope that Lenovo will release a BIOS update for the latest versions and hopefully it will be possible to reuse the flashing utility they will provide.

    About the "no whitelist" BIOS of the first post, did anybody already downgrade (or upgrade I should say) from a BIOS 5DCN90WW (v8.01) to the BIOS of the first post (v2.06)?

  11. Thanks, I was wondering if you got the error we get before getting the one you have. So strange that we get different errors with apparently the same system.

    - - - Updated - - -

    @En-TACT, in one of your posts you said that it was necessary to unblock all the files. When I extracted the archives, all the files seemed unblocked.

    On your machine, how did you do to unblock them? Maybe I missed something.

  12. Hi everyone!

    I have a Y580 that came with Windows 8 and the BIOS 5DCN90WW.

    I tried flashing the unlocked BIOS from the post #155. Thank you for your work svl7 :-)

    I tried with several configurations, but always got the same error when running the bat file to do a backup: Error 104: The two SPI flash devices do not have compatible command sets.

    The flash devices found are exactly the same as the one indicated on the screenshot from the post #163.

    I tried to execute the backup bat on several configurations:

    1. The stock Windows 8

    2. The stock Windows 8 after uninstall the antivirus

    3. When starting Windows 8 in "Safe mode" (even though it is not called like this anymore) with a command prompt only

    4. With Windows 7 x64 SP1

    @En-TACT, did you already get this error on your system? If yes, how were you able to avoid it?

  13. Hi everyone,

    I just got the Y580 yesterday with the 5DCN90WW BIOS installed. Will try the modded BIOS from svl7 as soon as I get a chance (this week-end probably). Just in case things go bad, do you have a link or a quick tutorial explaining the USB recovery method?

    Thanks a lot for your work!

  14. I was able to dump the BIOS with svl7's utility!! The trick was to run the *.exe's in admin mode and unblock ALL files, this prevents Windows 8 seeing them as malicious files.

    jovian, ShiftedView, I was not able to see clearly the error you get, but look at the post above, it might solve the problem.

    Apparently to unblock the files, you can right-click on it and click on "Unblock File" according to this link: How to Unblock Files in Windows 8

    Hope this can help.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.