scripts icon indicating copy to clipboard operation
scripts copied to clipboard

It is impossible to return to the standard firmware

Open Vany913 opened this issue 1 year ago • 12 comments

I want to go back to stock firmware, I lost my old firmware. Here are my specs.

17300213901106856469467019415816

I used the script in the sequence: Restore Stock Firmware>yes>yes>use recovery usb>my flash

result in the photo :(

17300214355851649354050846953462

Vany913 avatar Oct 27 '24 09:10 Vany913

Going back to stock firmware on devices which are past EOL is not supported by the script and not recommended at all.

What are you trying to accomplish exactly?

MrChromebox avatar Oct 27 '24 14:10 MrChromebox

I understand that my device is not supported. I want to go back to factory firmware to install rw_legacy. But I can't, because I didn't understand how important it was to save the old firmware file😓

Vany913 avatar Oct 27 '24 17:10 Vany913

What are my options for this?

Vany913 avatar Oct 27 '24 17:10 Vany913

download this, extract zip, copy to USB, use script to t restore. This is the stock firmware with RW_LEGACY firmware pre-packed, and the flags set to boot to RW_LEGACY automatically.

coreboot-Google_Ultima.7287.131.63_with_rwl.zip

MrChromebox avatar Oct 27 '24 19:10 MrChromebox

Yes, it worked☺️ Thank you! P.S. maybe it will be useful to someone else?

Vany913 avatar Oct 27 '24 20:10 Vany913

Sorry, I was able to set rw_legacy but if I press ctrl+l nothing happens

Vany913 avatar Oct 27 '24 21:10 Vany913

did you perform a ChromeOS USB recovery? If so, you erased the RW_LEGACY firmware which I preloaded for you

MrChromebox avatar Oct 27 '24 23:10 MrChromebox

I must have done everything wrong, what sequence of actions should I have done?

Vany913 avatar Oct 28 '24 00:10 Vany913

I selected the item firmware from a flash drive

Vany913 avatar Oct 28 '24 00:10 Vany913

I must have done everything wrong, what sequence of actions should I have done?

restore firmware using the file I provided

reboot

that's it. the firmware is set to boot from RW_LEGACY by default

MrChromebox avatar Oct 28 '24 00:10 MrChromebox

Can I update the file you provided according to the guide? https://docs.chrultrabook.com/docs/firmware/manually-flashing.html Again:(

Vany913 avatar Oct 28 '24 21:10 Vany913

if you are now able to boot ChromeOS, you can manually flash just the RW_LEGACY part of that file:

sudo flashrom -p internal -w coreboot-Google_Ultima.7287.131.63_with_rwl.bin -i RW_LEGACY

just make sure to use the full path to the file or copy it to the directory you run the command from

MrChromebox avatar Oct 29 '24 00:10 MrChromebox

Going back to stock firmware on devices which are past EOL is not supported by the script and not recommended at all.

What are you trying to accomplish exactly?

Hey sorry to necro this but you wouldn't have a copy of the stock firmware for the Acer Chromebook 314 (DROID) I could use to get back to stock?

Pajamaland avatar Nov 06 '24 23:11 Pajamaland

Hey sorry to necro this but you wouldn't have a copy of the stock firmware for the Acer Chromebook 314 (DROID) I could use to get back to stock?

I don't have stock firmware for any devices. The script provides an option to extract the generic stock firmware for a given board from the recovery USB. Alternatively, you can use coreboot's crosfirmware.sh script in util/chromeos/ to accomplish the same thing if you need an image to flash externally.

MrChromebox avatar Nov 07 '24 01:11 MrChromebox

Sorry for the absence, I think I downloaded the file and then rebooted. When I got a white screen that said "ChromeOS verification is disabled" I pressed Ctrl+L and it sounded 2 beeps, what does that mean?

Vany913 avatar Nov 07 '24 16:11 Vany913

I pressed Ctrl+L and it sounded 2 beeps, what does that mean?

it means that dev_boot_legacy is not enabled, or that the RW_LEGACY payload is not bootable

MrChromebox avatar Nov 07 '24 17:11 MrChromebox

what to do to fix it?

Vany913 avatar Nov 07 '24 17:11 Vany913

IMG_20241107_194005 here is the log while flashing

Vany913 avatar Nov 07 '24 17:11 Vany913

looks fine. now run sudo crossystem dev_boot_legacy=1

if still beeps, then need to flash RW_LEGACY differently I guess

MrChromebox avatar Nov 07 '24 18:11 MrChromebox

I was offered: PLEASE USE 'dev_boot_altfw' INSTEAD OF 'dev_boot_legacy' I did and it seems to have worked, ctrl+l now brings up a window I didn't see before and if you don't do anything it hangs with a black screen. And if you try again and then when you press esc you will be able to select the boot device. Should it be so?

Vany913 avatar Nov 07 '24 18:11 Vany913

yes?

MrChromebox avatar Nov 07 '24 19:11 MrChromebox

as long as SeaBIOS is loading via RW_LEGACY, then I would use the firmware utility script under ChromeOS to set the GBB flags to legacy boot + 1s default, then boot and install your OS

MrChromebox avatar Nov 07 '24 19:11 MrChromebox

I installed Ubuntu 24.04 to test and everything seems to work :). Can you write point by point what to do to make my OS default. P.S. on full firmware (uefi) i couldn't install linux if the kernel is newer than 4.15 and after a while the system froze and wouldn't boot anymore.

Vany913 avatar Nov 07 '24 19:11 Vany913

I installed Ubuntu 24.04 to test and everything seems to work :). Can you write point by point what to do to make my OS default. P.S. on full firmware (uefi) i couldn't install linux if the kernel is newer than 4.15 and after a while the system froze and wouldn't boot anymore.

run my script from linux, and select the option to set the boot flags. set to legacy + 1s default.

MrChromebox avatar Nov 07 '24 20:11 MrChromebox

I have no way to set download marks. IMG_20241108_003038

Vany913 avatar Nov 07 '24 22:11 Vany913

the script is not detecting the firmware type correctly, sigh. Google doing stupid shit on these older devices when booted in RW_LEGACY. what's the output of sudo dmidecode -t 0

MrChromebox avatar Nov 07 '24 23:11 MrChromebox

it doesn't seem to work :(

Vany913 avatar Nov 08 '24 17:11 Vany913

I don't know what that means

MrChromebox avatar Nov 08 '24 19:11 MrChromebox

here I enter the command and then the result IMG_2024-11-08-21-39-21-753 IMG_2024-11-08-21-39-49-326

Vany913 avatar Nov 08 '24 19:11 Vany913

the problem is Google deleted the version field when booting RW_LEGACY, so I can't tell what firmware you are running.

exit the script and run these commands: cd /tmp sudo ./gbb_utility --set --flags=0xa9 bios.bin sudo ./flashrom -p internal -w bios.bin --fmap -i GBB -N

if that works, you can reboot and it should auto boot to Linux

MrChromebox avatar Nov 08 '24 20:11 MrChromebox