I was trying to unbrick my computer using a SuzyQ but I accidentally skipped straight to flashing after installing my .bin file, am I fucked?
Can you be more specific?
What exactly did you do? Did you flash a file? If so: which one? What device do you have? Some more context on why you are unbricking would be helpful as well.
Sorry, I’m unbricking after my computer was unplugged during the UEFI Full Rom process. I was following the mrchromebox tutorial for unbricking, I chose to revert to the shellball firmware, after I downloaded that I accidentally skipped straight to the section about flashing without persisting the boards HWID and VPD
- What is the state of the machine now?
- What is stopping you from just redoing the process?
- Do you have the backup the script created when you originally flashed the full uefi firmware?
- Still bricked
- I’m fairly certain that I’ve messed something up, but I also haven’t gotten a chance to yet (like I said, I’m busy)
-
- No, that’s why I’m using shellball
So in that case you won’t get your old hwid back, but you should be able to make one up. I don’t know if the missing hwid in shellball is causing it to not boot right now.
That’s what I figured
you can absolutely flash an unmodified shellball/recovery firmware image and it will boot without issue. The HWID is just used for ChromeOS updates and configuration, nothing to do with booting.
I couldn’t get it to boot, so is it possible I just messed up during installation. Also I just remembered that i had to unplug my chromebook while i was doing the process because while it was charging the suzyq wouldnt detect and my battery was removed, so is it possible that might be a problem. I’m kind of a dumbass
the normal process is to disconnect internal and external power when flashing via SuzyQ, but if the firmware flash succeeded, then the device should boot.
OK, seems to have fixed itself overnight. Cant tell you what changed but I’m happy it did