2016-09-17, 02:34
Hey Matt,
Ok so I never said I couldn't press Ctrl+D, anything related to booting into ChromeOS was not a option for me, whenever I pressed Ctrl+D at the developer screen it did try to boot ChromeOS but then it said the owner had disabled boot in dev mode, the article below talks about the function, the person I bought it from should have un-enrolled it or removed it from whatever organization it got it's policy's from, way too long ago to do anything about now, I tried to find a picture of the screen on Google but couldn't.
https://bugs.chromium.org/p/chromium/iss...?id=412587
Not sure about the lucky part of the USB being enabled, are you saying that there's a number of Chrome devices out there where Ctrl+U is not enabled in the stock firmware ?, even if it's switched to dev mode ? or maybe it's a dev mode specific flag ?, because if the stock Legacy Boot does not have funtioning USB ports and stock firmware dev mode has no function to tell it to boot USB then it's kind of useless, even in my case, the coreboot firmware hands off to the Legacy Boot, so even though Ctrl+U flag was on, what initiated the boot off the USB stick if the Legacy Boot had non functioning USB ports ?, did coreboot skip the handover to Legacy Boot or something ?, just trying to understand what happened there because what you said has confused me quite a bit.
For quote 6 about not seeing anywhere that said coreboot firmware flash updates SeaBIOS, a small disclaimer or notice under the heading of "Install / Update: coreboot Firmware (standalone)" on the 1st page of this thread I think would make a world of difference, something like "NOTE: Flashing/updating the coreboot firmware updates SeaBIOS at the same time"
Regarding the bad firmware flash, is there a verification of any kind performed after it's flashed the coreboot firmware to ensure the data was written correctly ?, if not, then yeah a bad flash could be possible, he said that the device powers off immediately, I would have though a failure of the VBIOS which hangs the boot process would just hang, not cause it to actually power itself off.
PS: The stuff you've done is insane(the good kind), I don't want you to think I'm trying to knock you or have a go or anything.
Ok so I never said I couldn't press Ctrl+D, anything related to booting into ChromeOS was not a option for me, whenever I pressed Ctrl+D at the developer screen it did try to boot ChromeOS but then it said the owner had disabled boot in dev mode, the article below talks about the function, the person I bought it from should have un-enrolled it or removed it from whatever organization it got it's policy's from, way too long ago to do anything about now, I tried to find a picture of the screen on Google but couldn't.
https://bugs.chromium.org/p/chromium/iss...?id=412587
Not sure about the lucky part of the USB being enabled, are you saying that there's a number of Chrome devices out there where Ctrl+U is not enabled in the stock firmware ?, even if it's switched to dev mode ? or maybe it's a dev mode specific flag ?, because if the stock Legacy Boot does not have funtioning USB ports and stock firmware dev mode has no function to tell it to boot USB then it's kind of useless, even in my case, the coreboot firmware hands off to the Legacy Boot, so even though Ctrl+U flag was on, what initiated the boot off the USB stick if the Legacy Boot had non functioning USB ports ?, did coreboot skip the handover to Legacy Boot or something ?, just trying to understand what happened there because what you said has confused me quite a bit.
For quote 6 about not seeing anywhere that said coreboot firmware flash updates SeaBIOS, a small disclaimer or notice under the heading of "Install / Update: coreboot Firmware (standalone)" on the 1st page of this thread I think would make a world of difference, something like "NOTE: Flashing/updating the coreboot firmware updates SeaBIOS at the same time"
Regarding the bad firmware flash, is there a verification of any kind performed after it's flashed the coreboot firmware to ensure the data was written correctly ?, if not, then yeah a bad flash could be possible, he said that the device powers off immediately, I would have though a failure of the VBIOS which hangs the boot process would just hang, not cause it to actually power itself off.
PS: The stuff you've done is insane(the good kind), I don't want you to think I'm trying to knock you or have a go or anything.
