Original u-boot image [solved]

This forum is for supported devices using an ARMv7 Samsung SoC.

Original u-boot image [solved]

Postby antonl1911 » Sat Apr 12, 2014 9:14 am

Can someone upload this? I need to restore Chromebook to factory condition.
Last edited by antonl1911 on Mon Apr 14, 2014 9:16 am, edited 1 time in total.
antonl1911
 
Posts: 3
Joined: Mon Jul 08, 2013 6:40 am

Re: Original u-boot image

Postby AlexisTM » Sat Apr 12, 2014 4:28 pm

Download the image (I do not have it, so I can't give your the file) http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz

Navigate to the fat partition (On windows, use 7z) and copy the boot.scr file! :D
AlexisTM
 
Posts: 12
Joined: Thu Apr 03, 2014 9:21 am

Re: Original u-boot image

Postby WarheadsSE » Sat Apr 12, 2014 5:17 pm

If you have not altered the SPI by opening the box, you can use Google's, method for reflashing to stock from a USB.

Use the Chromebooks' 3-finger Salute (esc, refresh, power) and you will be present with the screen to reflash. Or, just mash spacebar at the developer mode warning during boot.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Original u-boot image

Postby antonl1911 » Mon Apr 14, 2014 8:05 am

Yes, I have altered SPI by opening the box (in fact, removing the screws was enough to disable hw protection for flash).

As it turned out, the verified uboot image is restored during chromeos recovery, at PostInstall stage.

To restore the factory condition I had to do the following:
0) Created system restore sd card with google utility.
* Run "vboot_twostop" cmd in u-boot, press ctrl+u to start restoration from sd card.
* After a while, it failed to restore with "Unexpected error". 3rd VT (Alt+F3) contained messages about write protection being enabled both in hw and in sw. So, there is no point in starting it with write protection still enabled.
1) Removed hardware write protection (by removing the screws from bottom). Reran restore procedure with vboot_twostop, then Ctrl+U. It successfully written the firmware, but failed on writing the 'ec' part.
2) Enabled hardware protection back and ran the restore procedure once more. Now it all went OK.

After that, ChromeOS is starting as it should. One minor problem is that I'm unable to disable developer mode, white screen is displayed for ~2 seconds.
antonl1911
 
Posts: 3
Joined: Mon Jul 08, 2013 6:40 am


Return to Samsung

Who is online

Users browsing this forum: No registered users and 1 guest