this post was submitted on 21 Aug 2025
349 points (98.9% liked)

memes

17066 readers
2328 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/Ads/AI SlopNo advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 2 years ago
MODERATORS
Tenthrow@lemmy.world
The_Picard_Maneuver@lemmy.world
The_Picard_Maneuver@startrek.website
349
Found in the wild (infosec.pub)
submitted 1 week ago by Uri@infosec.pub to c/memes@lemmy.world
29 comments fedilink hide all child comments
 
top 29 comments
sorted by: hot top controversial new old
[–] tetris11@feddit.uk 106 points 1 week ago* (last edited 1 week ago) (8 children)

Top tip: there's always a way to get to fastboot

Never lose hope, find the flashing tools and modes for your vendor and attempt to flash a recovery onto it. Somewhere out there (probably XDA) this information exists on the exact timings and button configuration needed to open that tiny flashing window where you can restore fastboot.

You might need to open the case and search for pins surrounding a chip with a TTL device (search for pinouts of your chip), but I guarantee you that the phone is always recoverable

[–] gigachad@piefed.social 28 points 1 week ago* (last edited 1 week ago) (2 children)

I tried everything for my Poco F1 in 2023, some Qualcomm tools, trying to go into EDL mode, using some weird firehose files with the MI flash tool. I read every fucking XDA thread. I even brought that phone to a shady repair service station near me, nothing worked.

The only option I did not use were some sus af indian Telegram channels that sold that service for 20 bucks.

Don't tell me the phone is always recoverable, because sometimes it is fucking not.

[–] tetris11@feddit.uk 7 points 1 week ago* (last edited 1 week ago) (1 children)

I've been exactly where you are, and can only say that despite it being maddeningly frustrating there is still always a way. It might require melting off a chip and soldering a replacement one on (with significant loss of data)

https://xdaforums.com/t/poco-f1-bricked.3968436/#post-80252328

You tried removing the battery panel and connecting the two test points to force EDL mode?

[–] AnyOldName3@lemmy.world 34 points 1 week ago (1 children)

You're well into Ship of Theseus territory once you're replacing major chips. You've not really recovered the phone, you've just replaced big chunk of it so it's not entirely the same phone anymore, just with extra hassle because you've not replaced the main board as a whole.

[–] tetris11@feddit.uk 7 points 1 week ago* (last edited 1 week ago) (1 children)

If the cost of Theseus replacing a mast incurred the cost of buying a new ship, then I doubt it would be his ship neither physically nor figuratively.

Chips are ridiculously cheap, and getting your local phone shop to resolder one on is about £30 and 30mins of your time worth spending

[–] AnyOldName3@lemmy.world 9 points 1 week ago (1 children)

I'm not saying it's not worthwhile to do this to fix a broken phone, just that if you have to do this, then the phone was bricked, and once you're replacing hardware, you're not just recovering it.

[–] tetris11@feddit.uk 3 points 1 week ago

that's a fair point

[–] lucario_owo@pawb.social 8 points 1 week ago (1 children)

Most of the time I find this stuff on 4pda. Sure it's in Russian and it requires an account to download files, but they delve much deeper into the device and usually you'll find working instructions how to unbrick stuff.

[–] tetris11@feddit.uk 3 points 1 week ago* (last edited 1 week ago)

never heard of this one, thanks?

[–] pewpew@feddit.it 6 points 1 week ago

Look up EDL mode for devices with a Qualcomm SOC, it usually requires opening the phone to short some pads but you might be able to buy a special cable that does it

[–] EtherWhack@lemmy.world 6 points 1 week ago

You might need to open the case and search for pins surrounding a chip with a TTL device (search for pinouts of your chip), but I guarantee you that the phone is always recoverable

Working with and building circuit testers, I can say those pins also very likely have test pads routed to them for when the board was originally programmed. Look for un-tinned, smallish solder pads that looks like a needle may have pricked them.

[–] somerandomperson@lemmy.dbzer0.com 5 points 1 week ago

Unlesa it's a samsung.

[–] SpaceNoodle@lemmy.world 1 points 1 week ago

Not if you flash over the earliest bootloader partition

[–] militaryintelligence@lemmy.world 1 points 1 week ago

Trust me bro, lying on the Internet is illegal

[–] Psythik@lemmy.world 1 points 1 week ago (1 children)

Even with water damage? Had to give up on my trusty old Fold 4 and make a claim. But it's all good cause I was able to take the money and put it towards a shiny new Fold 7 (best phone I've ever owned).

[–] tetris11@feddit.uk 1 points 1 week ago (1 children)

I wanna say yes -- once the phone is fully dried out and it never shorts, should be good to go after a few days?

[–] Psythik@lemmy.world 2 points 1 week ago

I could only get it to work for about 6 hours after a week of drying it out in the fridge. It bought me just enough time to back up my data before it died again for good.

[–] cappa@feddit.org 25 points 1 week ago

I still rember how I felt while bricking the first time a smartpgone, was my friends one, a Samsung S2 - I forgot the bug, but I guess the bootloader was wiped or similar. But with Jtag-tools it was possible to debrick.

Anyway - nice and funny error message, more of them please

[–] NeatNit@discuss.tchncs.de 14 points 1 week ago (2 children)

Where is this message coming from? It's obviously not written by Xiaomi. If fastboot isn't available, what is available to show this error?

[–] Uri@infosec.pub 27 points 1 week ago

It's a meme bro

[–] Wizard_Pope@lemmy.world 8 points 1 week ago (1 children)

You know it could literally just be an image????

[–] NeatNit@discuss.tchncs.de 9 points 1 week ago (1 children)

It's called suspension of disbelief! If this were real, could it work?

[–] xia@lemmy.sdf.org 3 points 1 week 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);
[–] MuteDog@lemmy.world 4 points 1 week ago (4 children)

WTF is that N key on that keyboard?? looks like an upside down U

[–] BananaIsABerry@lemmy.zip 3 points 1 week ago

Looks like the razer keyboard font.

[–] donnywholovedbowling@lemmy.dbzer0.com 3 points 1 week ago

I'd bet that's an HP omen laptop

[–] pipe01@programming.dev 1 points 1 week ago

That's a gamer N