Hi there,
I've been reading around for 2 days but am a bit overwhelmed by the amount of info all around and nothing fitting exactly my "issue".
I bought a "broken" switch off of ebay quite a while ago in order to try to fix it, but never got around to do so at the time (that's like 4 or 5 years ago...).
Now I just happened to find the switch on my pile of shame and thought I'd give it another go.
What the ebay seller probably saw as defective (and me at the time of first checking it), seems to be an AutoRCM and some form of broken/malformed eMMC.
When trying to start the switch (with or without Vol+), the screen stays black, but it's not recognized by TegraRcmGUI.
What I now found, was that when I remove the eMMC chip, the switch gets into RCM mode properly and I can inject payloads without issue.
After hot-plugging the eMMC chip back in, I can also dump and browse it with TegraExplorer and it generally seems to be readable (it just can't be plugged in during Boot).
Now the question is: is the eMMC somehow broken after all and I need to replace it, or could it be a software issue?
My hunch is that the seller screwed up an update and couldn't get it to run anymore, so decided to sell it, because:
- HW/Fuse info in hekate shows 12 burnt fuses - HOS 9.1.0 - 9.2.0
- but when checking the NAND Dump with NxNandManager or TegraExplorer (or simply launching into Atmosphere), the actual firmware on the eMMc seems to be 4.1.0.
TLDR:
I haven't quite read up about AutoRCM and fuses and updates, but saw hints here and there, that that's something to be careful with in order to not brick the switch.
Can someone point me into the right direction on how to proceed?
From what I saw, since I have an unpatched Erista, there should be no reason to stay on an old firmware?
Do I rebuild the eMMC?
Do I boot into AMS and update to a new version there?
What's the way to get this to work normally with the eMMC plugged in and the console closed?
EDIT:
after closer inspection, it seems that AutoRCM is actually not active. So my new theory is that because of the fuses/the sysNAND firmware the switch refuses to boot anything and me removing the eMMC causes a panic and actual RCM Mode.
I'll try enabling AutoRCM and creating an EmuMMC and update it to current Version.
EDIT2:
As mentioned in the first edit, I actually enabled AutoRCM after figuring out more about everything.
Now it actually works without me yanking out the eMMC.
Afterwards I updated both sys and emu to 18.1.0 and now everything works as expected.
I could delete the thread, but maybe someone in the future might have similar symptoms
I've been reading around for 2 days but am a bit overwhelmed by the amount of info all around and nothing fitting exactly my "issue".
I bought a "broken" switch off of ebay quite a while ago in order to try to fix it, but never got around to do so at the time (that's like 4 or 5 years ago...).
Now I just happened to find the switch on my pile of shame and thought I'd give it another go.
What the ebay seller probably saw as defective (and me at the time of first checking it), seems to be an AutoRCM and some form of broken/malformed eMMC.
When trying to start the switch (with or without Vol+), the screen stays black, but it's not recognized by TegraRcmGUI.
What I now found, was that when I remove the eMMC chip, the switch gets into RCM mode properly and I can inject payloads without issue.
After hot-plugging the eMMC chip back in, I can also dump and browse it with TegraExplorer and it generally seems to be readable (it just can't be plugged in during Boot).
Now the question is: is the eMMC somehow broken after all and I need to replace it, or could it be a software issue?
My hunch is that the seller screwed up an update and couldn't get it to run anymore, so decided to sell it, because:
- HW/Fuse info in hekate shows 12 burnt fuses - HOS 9.1.0 - 9.2.0
- but when checking the NAND Dump with NxNandManager or TegraExplorer (or simply launching into Atmosphere), the actual firmware on the eMMc seems to be 4.1.0.
TLDR:
- unpatched Erista with AutoRCM
- Black screen upon bootup, but not recogizable by pc
- RCM works when I remove the eMMC
- eMMC works after booting into hekate and hot-plugging it back in
- Fuses say HOS 9.1.0 - 9.2.0
- eMMC firmware is 4.1.0
I haven't quite read up about AutoRCM and fuses and updates, but saw hints here and there, that that's something to be careful with in order to not brick the switch.
Can someone point me into the right direction on how to proceed?
From what I saw, since I have an unpatched Erista, there should be no reason to stay on an old firmware?
Do I rebuild the eMMC?
Do I boot into AMS and update to a new version there?
What's the way to get this to work normally with the eMMC plugged in and the console closed?
EDIT:
after closer inspection, it seems that AutoRCM is actually not active. So my new theory is that because of the fuses/the sysNAND firmware the switch refuses to boot anything and me removing the eMMC causes a panic and actual RCM Mode.
I'll try enabling AutoRCM and creating an EmuMMC and update it to current Version.
EDIT2:
As mentioned in the first edit, I actually enabled AutoRCM after figuring out more about everything.
Now it actually works without me yanking out the eMMC.
Afterwards I updated both sys and emu to 18.1.0 and now everything works as expected.
I could delete the thread, but maybe someone in the future might have similar symptoms
Last edited by Kaesebroetchen,
