Recent content by Endracion

  1. E

    Creator of atmosphere retiring

    You've certainly left your mark, thanks for all your hard work, it's been much appreciated and good luck for your next chapter.
  2. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Nobody has any input on this?
  3. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Got a switch lite from a friend, it shows the charge icon for a second, if I start it, Nintendo logo shows up, then nothing. From a quick search, it's a good idea to install the picofly to see if it'll load into Hekate for diagnosis, but after installing it, I immediately get ===* BCT copy...
  4. E

    Hekate Overburnt Fuses 29 | 24

    Thanks for the clarification, I also don't know what they did to burn more than normal as they explained they only ever used sys-mmc with cfw and wasn't booting the original system.
  5. E

    Hekate Overburnt Fuses 29 | 24

    This is the first time I encounter this. Someone brought me a switch that shows 29 | 24 - HOS: Overburnt I'm not too sure how to fix this, if it's even fixable, as the max number burned should be 21 as far as I know. Would rebuilding the NAND from a donor fix something like this? I can't seem...
  6. E

    Picofly AIO Thread

    I've been using FW 2.75 for a good long time for my installs, it's unclear what changed but I see that the latest version is 2.80; does it glitch faster or better or something?
  7. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Maybe someone here will know, since we open so many switches - what is this and where does it go (Switch V2)? Was loose in the back.
  8. E

    Opened switch V2, this fell out, what is it, where does it go?

    I've opened many switches, but this is the first time a piece just falls out. I believe it's from the side, but I can't figure out what it's called or where it goes exactly - can anyone help identify this piece?
  9. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    So I'm not crazy right, this is ==* long long short, so BCT error? Mosfet removed does this too. I did end up replacing the mosfet, even though the reading was seemingly correct and it solved the issue.
  10. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Thanks for that! So I'm reading over 1.123M Ohm on Drain to Gate and the same from Source to Drain, would that mean that it's functional as expected and I messed something else up? To add some more context, I've done all the past 20 installs with a rear mosfet.
  11. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Just checking here to confirm that the "CPU always reach BCT" error is indeed always due to the mosfet - first time I get this error, but I only have one mosfet left, and I'm guessing this one might just be defective? Is there any way to test it before I scrap it and use my last one?
  12. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Darn, I just tried with a new adapter and it's still the same, I'm not looking forward trying to removing the resin from the CLK to see if that's the issue now... I'm not sure what else to attempt other than resoldering from zero. I have the 100/100/47 Ohm resistors on the Zero too. EDIT: Well...
  13. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Well I reinstalled the adapter, although if the values can't be trusted, I'm not sure what to do next, the adapter is all I have access to right now anyway and it had been working before too. It's interesting to know that even though the error suggests it's something else that it's indeed still...
  14. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    And I'm back with another diagnosis problem. An OLED came back because it wouldn't go into hekate anymore, it would do the short long long, which is *== No eMMC CMD1 request (poor wiring, or dead CPU) but it boots into OFW, just skips the chip. So I checked the DAT0, reads 0.8 fine, then I...
  15. E

    Hacking Hardware Picofly - a HWFLY switch modchip

    Had tried that, didn't work either. I ended up taking everything off and starting from scratch and it worked, but I couldn't identify the issue and was quite panicked in the moment.
See more