Closed Wildtick closed 1 year ago
chromebook model:Hp 11 g8 ee
try pressing "recover system" before installing halcyon
didn't work showed the same error
Use a bigger USB, that happened to me too.
@Sincereham222 just tried a 32gb one that had the same results...
The video does not show what is wrong after the not enough space thing it still installed when I had that error I was still able to boot E-Halycon Normally
Well after i press the boot into semi-theathered and it said E mode wasn't active so i just assume it's because of the error
then when i reboot chromeos breaks and i need to recover
The reason why it says e mode wasnt active is bc AS SOOON as you plug in the usb you need to just keep spam clicking the e key on your keyboard and when you see the HE Chromeos screen keep clicking e for at least 5 secs. After that now u can boot in
I'll try again when i get home but i doubt i'll see any change
if you could if the issue continues could you send a new video of the whole process then maybe I might be able to see what went wrong you dont need to do the installation again since once you do it once, you'r good.
Thanks for the tip i was able to unenroll!!!
though i still have one question when i try to use fakemurk so i could be half enrolled it broke because i wasn't in dev mode. Is it possible to use fakemurk after E-halycon? @CoolElectronics @H644b
I do not think it is possible I do not want to risk my school Chromebook on a chance so I do not know for sure. What I know though is that based off my very slim amount of knowledge, E-Halycon does not actually unenroll you on the main Chrome OS. Sh1mmer does that. E-Halycon, im pretty sure, is basically like as if you are running debian linux on chrome os dev mode where the actual Chrome OS is there and the linux is just what you see. This is why when you restart your chromebook it goes to developer mode and breaks unless you have a recovery usb. It goes there since it tries to go back to the original operating system but it is glitched so it breaks.
Also, if you want to keep dev mode but make it seem like you are enrolled, just do not recover and re install e-halycon and then boot. It will put you in dev mode while still being enrolled. This basically serves the same purpose as fakemurk.
but if i re-enter e-halycon after using it, it doesn't allow me? gives some errors...
oh well if you see the issue I had, you can see that before I did all the other things, I had dev mode but was enrolled. I was trying to find a way to unenroll and I found it.
Oh well lucky you, maybe an exploit that isn't fakemurk will come out and get me dev mode while being enrolled
I have just realized. If you search up a downgrade video and downgrade your chrome os version, you will be able to use Sh1mmer on its own therefore keeping it working even if you reboot your chromebook and also you will be able to use fakemurk. I think that is the better way to go. E-Halycon is not that stable and it does not save your files on reboot.
I'm on 114 i can't downgrade past 112 i would need a chromebook thats on >111
Im on 116 :( I was so enthusiastic but then I tried and I got an error message saying you are using an out-of-date Chrome OS Recovery image. @CoolElectronics Do you know how to bypass this without turning off verification. Cause I turned it off but then it would not reboot into chrome os after it recovered.
Also @CoolElectronics when I went on the sh1mmer website I saw I needed to turn off Wp and a quick search found me on your website about shorting the chip. I took and flipped the motherboard but now I dont know how to short it. Wdym by saying to use a pencil. Its too big for such a small chip
I just realized lucky me my lenovo 300e 2nd gen has wp screw instead of chip welp back to assembling
STILL DOES NOT WORK LIKE HOW NOW I AM RAGING. @CoolElectronics plssssss helpppp. Even when I remove screw and assemble it still not working
@CoolElectronics Never responds
💀
On god, stop spamming the repo for support, repo maintainers don't spawn out of thin air
https://github.com/MercuryWorkshop/RecoMod/assets/110534522/671eaa6b-af22-4f7a-a81b-3c5f39e1db94
gives me the error of "dd: error writing '/dev/mmcblkdp2'"