Come ooooooooooooon more recent version exploit...... *rolls dice*Option 2 is closer.
I don't want to be the kind of dev that talks too much about what they're working on (getting people all hyped up) without talking about any plans for release, so until I know what a release schedule looks like I'll be keeping short on details. Lots of work to do, still, anyway.
Let's just say yesterday was a big day and leave it at that.
Lol okit uses the switch array overflow in the 0x22 integer located in the kernal
My boi. Michael gets all the attention he wants. He earned it a long time ago. If he tweets something like this, he's made progress.What a useless attention seeking tweet.
Blue indicated nothing on Wii U, but red was used to indicate IOSUI recall something from wiiu pics, red signified something. Blue I forget what blue indicates.
You've been naughty though.SOME HOMBREW WOULD BE A NICE CHRISTMAS GIFT FOR THE SWITCH LOL
They'll have to move on from 1.0.0/3.0.0 at some point, as the number of units will be super low.SciresM, tells us a long while back that 'all the good stuff' will happen on 1.0.0 firmware? Right?
SciresM, tell us to all hold tight and now shows a bootrom error screen and tells us it's not an error 'nudge, nudge, wink, wink'.
Read between the lines folks. Good times ahead for those who paid attention to the reputable devs.
Do you get it? Then you'll get it.....otherwise enjoy what you have.....
I just got a Blue Screen at boot too just like OP. I was messing with the eMMC NAND and suddenly got this. Not sure if that was really the cause but after trying to restore the original NAND contents, I still keep getting the Blue Screen.
Can anyone confirm what the cause of this is?
My post wasn't at boot.
It's the application of a high enough voltage to the liquid crystal cells corresponding to red and green, so that these components of the backlight are blocked.Could you clarify what causes the blue screen?