09-04-2016 10:47 AM
no have boot windows 7 in stick install windows 8.1
include usb instalatin windows 7 no indication pls help my
To boot from other than the installed OS, you will have to turn off "Secure Boot" in the BIOS.
09-04-2016 12:33 PM - edited 09-04-2016 12:36 PM
You need to have the USB memory stick already inserted, before you reboot the Stick, but you probably did that. Also, since you have both a USB keyboard and the bootable USB memory stick connected, that means you are using a USB hub. Make sure you use a powered USB hub.
Also, the Stick will not boot a USB memory stick that is formatted for NTFS. It must be FAT or FAT32.
I don't remember exactly the steps I did after I disabled Secure Boot, in order to get a USB memory stick to boot. Search around in the BIOS settings. You may (I don't remember) have to enable "Legacy Boot" or something like that.
09-05-2016 11:48 AM
Did not work at all the problem is the machine doesn't start. I just see the blinking light. I've escelated it with Lenovo services to se what will be done otherwise I will never again buy their products and will **bleep** make sure that no one else buys from them and or knows of the issues I have had the with the stick.
10-01-2016 07:40 AM
11-19-2017 01:12 PM
I'm in the same situation with my Lenovo Stick, but I'm out of the warranty period.
It was working until I noticed there was a BIOS update available here on the Lenovo site. I followed the procedure to update the BIOS from within Windows but it appears that failed and now I just get the power light cycling on/off about every 10 seconds. Nothing comes up on the TV screen at all. Tried all options available to try to get into the BIOS anyway, but no luck.
It is unacceptable that Lenovo is offering a BIOS update and when you follow the procedure it bricks your device! DO NOT TRY TO UPDATE THE BIOS FROM WITHIN WINDOWS (despite the fact that Lenovo documents this as an option)!
Lenovo, you need to make this right!!
02-11-2018 01:12 PM
I know this is an old thread but I want to provide some information that will enable this issue to be put to rest.
I, like others bricked my Stick when updating the bios to O27KT10A. I used the UEFI shell method and it still crashed. I remember glancing at the error message and it was the spi flash write error. After that brick. the stick will not boot.
I have the equipement to flash in circuit the 25Q spi flash chip so I removed the inside headers from the Bin using extractor and checked the bios file using the inside tools and it all checked out. I got an FD size of 4.7MB (the file is 4.78MB). close enough.
I proceeded to open the stick to gain acces to the spi flash chip and I checked the type. It is a winbond 25Q16DWSIG. At that point I realised what had happened. the chip is only a 2MB chip. There is no way a 4.7MB bios will fit in there ! this is an odd chip the D means that it can output 2 bits in parallel for fast read. Something not used by the Intel Atom. normally on all the Atom devices from China you find 8MB devices like the INTEL stick which has a 25Q64FWSIG.
I think somebody scammed somebody. I wonder if the Chinese manufacturer just put 2MB chips because thats all he got at the time and the original bios could fit and he did not care if it died later.
Anyway the result is that if you got a stick with that spi chip, it is dead. It will never be able to load that BIOS. Just for the fun of it I will remove the current SPI chip and get an 8MB one. program the BIOS and solder the new chip. I will see if that revive the stick.
I hope this is usefull to others.
02-11-2018 05:44 PM
My first Stick had part number 90F20000US & it bricked on attempting to flash the BIOS. When it was replaced under warranty, I received one with part number 90F20001UK. Since I wanted to flash the BIOS in that one before it ran out of warranty, I did so & was successful.
I then upgraded the pre-installed Win 10 Home to Win 10 Pro, enabled BitLocker (encryption) & the stick has been working fine running 24/7 ever since.
So, people should check their part number before attempting to flash the BIOS.
09-18-2019 03:11 AM
@fifcic, I do confirm your findings !
I've got Ubuntu 19.04 installed on my Stick 300-01IBY (with bios O27KT07AUS) and wanted more BIOS settings than just date and times (as in O27KT07AUS version), like booting on power-on. But before upgrading BIOS version I wanted to check I won't get any issues...
With Linux/Ubuntu , there is an utility called flashrom (installation: "sudo apt-get install flashrom") that can give information about the flash chip without opening the box.
With the command:
sudo flashrom --programmer internal
You'll obtain this result about the flash chip storing the BIOS, and here it is on my Stick 300-01IBY:
Found Winbond flash chip "W25Q16.W" (2048 kB, SPI) mapped at physical address 0x00000000ffe00000.
And you're right, it's a 2MB chip, and so a 4MB can't be flashed on it. The latest BIOS update from Lenovo o27kt10aus with a O27KT10A.BIN file of 5.9MB (4.7MB without headers) will never fit on it, it will just make the stick a brick.
I'm pretty sure Lenovo was well aware about it from the beginning, and it's probably why this product got only 3 months warranty. (This product was one shot sell-and-forget).
Anyone interested in updating the BIOS, should first check the Flash Chip of his stick before proceeding. If it's a 2MB chip, it's a no-go ! One can do it with a live version of Ubuntu respinned:
http://linuxiumcomau.blogspot.com/2017/06/customizing-ubuntu-isos-documentation.html (Respin: because Atom CPU is 64bits and can run 64bits OS, but it is limited to only 32bits bootloader).
09-20-2019 08:59 AM
Well, after digging a bit more... it seems the situation is a bit more complex !
I've extracted both dumps from the Windond Chip and from the mmcblk1boot0 partition on the eMMC module, and checked them with UEFITool.
The UEFI/BIOS is not totally stored in the Winbond Chip, but just a minimal part of it. In this chip there is a minimal BIOS with some interesting features such as RecoveryOtgInit, CrisisRecoveryPei, FirmwareAuthenticationPei and MmcBiosLoaderPei,... But no reference of my current BIOS version in it.
Yes "MmcBiosLoaderPei", because in fact the main part of the UEFI/BIOS is stored on a 4.2MB locked partition of the eMMC module "mmcblk1boot0".
When checking the mmcblk1boot0 dump image with UEFITool, I'm able to find inside it the reference of my BIOS version (O27KT07AUS) and references from Insyde (a well known BIOS vendor). So it's definitely the working UEFI/BIOS from Lenovo that is stored on eMMC module.
The good news is that the minimal UEFI/BIOS stored on the Winbond chip has a recovery feature available. So users with bricked Stick-300 should definitely give a shot to Insyde BIOS Recovery methods