i get the nintendo switch logo with the joycons above only when injecting fusee, if I use hekate to launch cfw it shows a hekate launch image then the screen turns off.
I will try ubunto now and see
Thanks
i get the nintendo switch logo with the joycons above only when injecting fusee, if I use hekate to launch cfw it shows a hekate launch image then the screen turns off.
I will try ubunto now and see
Thanks
Followed the guide and installed linux. Went to boot it and it came up with the splash screen for linux then backlight went off and nothing. Left it for a bit to see if it was setting up still but nothing.
Assuming this isnāt a setup issue then itās pointing to hardware problems again.
Can you measure the resistance to ground on the inductors surrounding the main PMIC as well as 3V3PDR (this can be found at the large capacitor near P13 or pin 6 of M92)
just had a thought, the battery didnāt seem to hold charge very well and thought it seemed to crash when needing more power so changed batteries and can now boot into linux and wifi works, can also boot into cwf so really happy now I can move forward
What would you suggest to do now to try to get original firmware back on it and working?
Thatās very strange, the previous battery was reporting normal voltage and [Uncalobrated] decent capacity in Hekate, if you have an ext Li battery charger (ideally one which can test capacity) then I would use that to verify this problematic battery, if it still exhibits the same symptoms then perhaps there is an issue with the central conductor either at the batteries connector or the wire.
Great news
I would remove the jig and attempt to boot stock OS, donāt connect to the internet if it boots, afterwards boot into Hekate, the fuse count should now hopefully reflect the OS version on the EMMC, afterwhich Iāll provide instructions on how to fully wipe the console with a payload which will decrease the chances of this unit being bannedā¦ that is, if it isnāt already - of which the chances are high as the previous owner was evidently running CFW on sysnand.
thanks but stock OS still doesnāt boot for me. Does it matter that it was an exfat version 9.2 fw installed?
and that was different to the boot 0 which was 9.1
Did the fuse count remain the same following attempting to boot it?
Exfat is merely indidcating the OS driver support for exfat SD cards as far as I remember
Donāt worry about that, this is just a difference between the info reported by boot0 and prodinfo and is normal
If the fuse count remains unchanged, I would attempt to disable autoRCM on the boot0 partition with NXnandmanager and write that altered boot0 back to the EMMC using Hekate (or mounting the partition over USB and wrting it that way), keep your original unaltered boot0 safe and sound as if this doesnāt work then write the original partition back. This is all just in case Hekate is preventing autoRCM from being disabled for some reasonā¦
Failing all that, I would probably attempt an offline update to the next FW version up from within a CFW using Choi or Daybreak (for ease) then doing a full system wipe using Haku33 then a full wipe from the Nintendo service menu following that
Thanks for the info. I disabled rcm on boot0, restored it then backed it up again and now not auto rcm on the file but still doesnt boot.
Used hekate to launch stock fw and it did, it showed as 9.2fw so shut it down and went back to hekate and fuses still at 10
hekate says āBurnt fuses (ODM 7/6): 10 - 0 (HOS: 8.1.0 - 8.1.1)ā if that means anything
also on the battery, the other one showed 99% and 725mah capacity
this one shows 48% 2141mah with capacity of 4450 so other one definitely seems no good
This is very odd behaviour, fuse should be burned (to whatever the EMMC OS is currently on ) the moment stock OS is attempted to boot (non RCM/no jig then hitting the power button) I canāt really explain whatās going on, I mean unless you have a more obscure hardware fault which Hekate is able to get around but which would prevent stock os from even attempting a boot thus preventing the fuse from burningā¦
when your booted into stock OS via Hekate, what is the charging current?
Can you take a photo of the console info section in Hekate?
Thatās normal, battery often needs semi cycled before Hekate accurately reports the battery capacity. I would attempt charging the battery externally if you have an ext charger and seeing once again if the console will boot CFW or stock os via Hekate with this suspected bad battery as this may well may be pointing to some other intermittent problem if the suspected bad battery suddenly starts working fine.
Failing all of the above, I would attempt to update the OS within CFW as mentioned earlier
I couldnāt get it to boot from off, only from within hekate so donāt know if that skips fuse check?
Charging current 15v 0.46A
Sorry I was navigating the Hekate menu from memory, can you also provide a pic of the HW/Fuses section
Yes Hekate skips the fuse check
if your within the stock OS/CFW (you will not see fast charge current from within Hekate only the OS) charging current should be higher than that provided the battery isnāt fully charged, can you let me know the charging current with a standard 5V supply? - provided the battery isnāt fully charged it may be indidcating M92 issues or M92 install issues
Pic below
I have updated using daybreak to 10.04 and it said everything went ok, however no I cant get CWF or OFW to load from Hekate.
I will keep playing around with it later to see if I can get any further
Not to worry, just write back the whole backup you made at the very beginning and you will at least be where you left off.
Something very odd here going on with the fuses and Iām not sure what it is. Once youāve restored the backup and are back in CFW/OFW let me know that charging currentā¦ perhaps it will provide a clue
will do what you suggest and let you know. Would it matter if I selext normal or exfat when installing if my goal is an original switch (assuming its not banned)?
Doesnāt matter, itās installed officially after a certain OS version through the legit update, if you choose not to install it with daybreak it will simply be updated later via the nintendo server (at least as far as I remember)
Just make sure to keep your original backup somewhere safe, I get the feeling your going to be going forward and backwards a lot, though ultimately I donāt think itās going to make a difference, I think there is an underying hardware issue at play here, so reckon just revert back to the previous backup via Hekate (or mounting the EMMC over USB and wrtiting back the backup) and weāll see whatās going on from there
Also, just add, I notice from your previous pic that the console was running over 50C, probably not a huge deal but I donāt like letting it run over 40C without a heatsink, so if your thinking you might be operating the system and the temp will go beyong that after an extended amount of time, it might be worth fitting the heatsink back on
Thanks @Severence, will put the heatsink and fan back on before continuing. Just copying the backup files over to the sd card then will prob call it a day and resume play in the morning
Hi again, update timeā¦
Restored the backup of EMMC and booted to hekate. Voltage readings were 15v 0.48a 5v 0.47a
Tried to boot to cfw and backlight turned off and nothing. Tried to stock and it loaded fine but through hekate only, not from power off so didnāt affect fuses. Tried charging in stock fw and got 15v 1.4a 5v 0.79a which seemed good.
I have tried putting all the atmosphere files on the sd again and still wont boot to custom so now I am even more confused. I thought if I could get back on, I would try downgrading to 8.1 to match the fuse count and see if that would do anything but canāt even try without getting into custom firmware again
Strange, not that I think it would matter as afaik Hekate bypasses this, but have you also restored your original unaltered boot 0? (the one you didnāt modify by NXNanManager)
Yeah seems fine
I think maybe the next course of action might be to generate the partitions using Choidujour on PC using somebody elses keys but with your BIS keys swapped in which will generate all partitions from scratch, perhaps a partition is corrupt which Hekate is somehow able to bypass, boot 0 springs to mind but Iām not sureā¦
Guide here
https://switch.homebrew.guide/usingcfw/manualchoiupgrade.html
EMMCHaccGen will also work and might be a little easier to follow but up to you
Iād probably downgrade to pre 8.XX and then use daybreak or choi from within CFW to bring yourself back up to 8.1/8.2 (whatever your prodinfo reported earlier) and then see if stock OS boots without the need for RCM/Hekate
Will try all this thanks
I have just tried (when in stock from hekate) to dock it using a usbc hdmi adapter (works on my sons switch) and the screen goes off but doesnāt show on the tv. Could this point to something stopping it from booting from off? Longshot maybe but will try anything