Found in the wild
-
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
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.
-
This post did not contain any content.
WTF is that N key on that keyboard?? looks like an upside down U
-
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?
You know it could literally just be an image????
-
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.
that's a fair point
-
You know it could literally just be an image????
It's called suspension of disbelief! If this were real, could it work?
-
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.
The Chip of Theseus.
-
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
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.
-
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
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).
-
WTF is that N key on that keyboard?? looks like an upside down U
Looks like the razer keyboard font.
-
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).
I wanna say yes -- once the phone is fully dried out and it never shorts, should be good to go after a few days?
-
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
Trust me bro, lying on the Internet is illegal
-
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
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
-
I wanna say yes -- once the phone is fully dried out and it never shorts, should be good to go after a few days?
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.
-
WTF is that N key on that keyboard?? looks like an upside down U
I'd bet that's an HP omen laptop
-
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.
never heard of this one, thanks!
-
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
wrote last edited by [email protected]for the specific xiaomis this kind of thing happens to, there is a leaked tool to restore the bootloader. there often is.
-
WTF is that N key on that keyboard?? looks like an upside down U
That's a gamer N
-
It's called suspension of disbelief! If this were real, could it work?
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);
