Quote:
Originally Posted by doomgoatman
I believe that the hardware between the Go Color 7 gen 2 and the Go 7 Monochrome are the same except for the screen.
Go 7 Monochrome specs can be seen here if you scroll down a bit: https://www.techradar.com/tablets/er...ox-go-7-review
Go 7 Color gen 2 specs can be seen here if you scroll down a bit:
https://www.techradar.com/tablets/er...-gen-ii-review
No idea about the stock firmware though. Purely speculatively I think they're the same given that I see some options for color settings in my Go 7 Monochrome that don't actually seem to do anything. |
https://blog.tho.ms/hacks/2021/03/27/hacking-onyx-boox-note-air.html
https://gist.github.com/fardjad/97ba...953b3d359bb918
The two posts that inspired the tutorial I used suggest that the bootloader should have already been unlocked by default.The buduroiu post makes no mention of a locked or unlocked bootloader status.
Given I'm stuck in fastboot with no EDL cable and the flashing commands not working I did some digging and found this, which almost certainly reveals the culprit:
Code:
root@computer:~# fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
It seems likely that at some point after the publishing of these posts Onyx published an update that locked the bootloaders by default. A device trying to boot a patched magisk image with a locked bootloader will almost certainly trip the AVB mechanism and brick itself. (I consider myself lucky having fastboot access) Now I'm a diligent person and I try to verify what I'm doing before executing random commands from the internet, and if there was even a passing remark of an unlocked bootloader I'd have stopped and checked what I was doing. It's only after looking at the original posts that I saw this and I find it irresponsible for the post writer to omit this detail. (even though ultimately it's my responsibility to not cause thermonuclear war while tinkering with my devices)
Either way I will try the fairphone bootloader method to get my device in a working position before attempting root again, thank you for your insight.