▲ 363 ▼ Found in the wild (infosec.pub) submitted 11 months ago by Uri@infosec.pub to c/memes@lemmy.world 32 comments fedilink hide all child comments
[–] Wizard_Pope@lemmy.world 9 points 11 months ago (1 child) You know it could literally just be an image???? permalink fedilink source parent hideshow 2 child comments replies: [–] NeatNit@discuss.tchncs.de 10 points 11 months ago (1 child) It's called suspension of disbelief! If this were real, could it work? permalink fedilink source parent hideshow 2 child comments replies: [–] xia@lemmy.sdf.org 3 points 11 months ago In theory, yes. There is a first-stage bootloader (that actually finds, loads, verifies, and jumps-into fastboot) baked into the hardware (implemented in fuses and ROMs [like REAL roms, not "flashable" ROMs]), and AFAIK it cannot effectively be modified after the phone is manufactured, so they try to keep it as simple as possible. So if it were real, the psuedocode would be something like this: var fastbootPartition=locateFastbootPartition(); if (fastbootPartition == null || !verifySignature(fastbootPartition)) { // AFAIK, this code block is already a thing in production, but the // message is more like a "signature failed" or "corrupted" than // a "you done goofed". displayRudeMessage(); halt(); } var fastbootAddress=load(fastBootPartition); jumpTo(fastbootAddress); permalink fedilink source parent
[–] NeatNit@discuss.tchncs.de 10 points 11 months ago (1 child) It's called suspension of disbelief! If this were real, could it work? permalink fedilink source parent hideshow 2 child comments replies: [–] xia@lemmy.sdf.org 3 points 11 months ago In theory, yes. There is a first-stage bootloader (that actually finds, loads, verifies, and jumps-into fastboot) baked into the hardware (implemented in fuses and ROMs [like REAL roms, not "flashable" ROMs]), and AFAIK it cannot effectively be modified after the phone is manufactured, so they try to keep it as simple as possible. So if it were real, the psuedocode would be something like this: var fastbootPartition=locateFastbootPartition(); if (fastbootPartition == null || !verifySignature(fastbootPartition)) { // AFAIK, this code block is already a thing in production, but the // message is more like a "signature failed" or "corrupted" than // a "you done goofed". displayRudeMessage(); halt(); } var fastbootAddress=load(fastBootPartition); jumpTo(fastbootAddress); permalink fedilink source parent
[–] xia@lemmy.sdf.org 3 points 11 months ago In theory, yes. There is a first-stage bootloader (that actually finds, loads, verifies, and jumps-into fastboot) baked into the hardware (implemented in fuses and ROMs [like REAL roms, not "flashable" ROMs]), and AFAIK it cannot effectively be modified after the phone is manufactured, so they try to keep it as simple as possible. So if it were real, the psuedocode would be something like this: var fastbootPartition=locateFastbootPartition(); if (fastbootPartition == null || !verifySignature(fastbootPartition)) { // AFAIK, this code block is already a thing in production, but the // message is more like a "signature failed" or "corrupted" than // a "you done goofed". displayRudeMessage(); halt(); } var fastbootAddress=load(fastBootPartition); jumpTo(fastbootAddress); permalink fedilink source parent