Not if there's a new revision and has a quirk.
The thing is, is that really a new revision? What switch version you have?
Also do you see any SD card performance degradation in switch? I mean 4 times lower speeds than PC?
The thing is, is that really a new revision? What switch version you have?
Also do you see any SD card performance degradation in switch? I mean 4 times lower speeds than PC?
No performance problems with the newer 64gb exFAT card. The 32GB one was always slow. Both worked in RCM on that same Switch until I replaced the SD reader, I'll attach a picture of what I replaced to avoid confusion. The Switch is a launch model and I was able to use hekate before the slot broke.
edit
Now I'm getting a new error.
Failed to init SD card
Make sure that it is inserted
If I try to enter the launch menu I just get booted into Switch OS where the card is visible and usable.
Attachments
Last edited by kamo,
I'm asking for performance degradation because 2 things hekate's driver does not support:
- SDSC cards (2GB and less)
- 1 bit data bus (slow mode)
Basically, a card can fall into this mode if the lego connector or the data pins are not OK. For example if a card is a U3 (~90MB/s read) it can fall to ~20MB/s.
But you can't test this with hekate (untrained DRAM is the bottleneck).
It is easy to check if it's the lego connector, by applying pressure on it and trying to run hekate and a Backup.
And you can do a visual check on the pins inside with a torchlight.
By lego connector you mean that thing that I connected to the mainboard? If yes, I could check that later.
Thanks for your work! I have some questions:
1. Does Hekate need an unit with "exFAT update" to use SDXC card for non-partial (one 32 GiB file) eMMC RAW GPP backup? Can it use an exFAT card (formatted on a PC) regardless of the unit software?
2. Is partial backup (set of 2 GiB or 1 GiB) mergable? Can one make partial backup on FAT32 card, copy it to a PC, merge to the 32 GiB file with 'cat' command and restore from an exFAT card?
1. Does Hekate need an unit with "exFAT update" to use SDXC card for non-partial (one 32 GiB file) eMMC RAW GPP backup? Can it use an exFAT card (formatted on a PC) regardless of the unit software?
2. Is partial backup (set of 2 GiB or 1 GiB) mergable? Can one make partial backup on FAT32 card, copy it to a PC, merge to the 32 GiB file with 'cat' command and restore from an exFAT card?
- As stated in OP, it has its own driver and does not care what switch os version you have.
- As stated in OP, it is and there are instructions there and scripts to do it in the repo's release section.
Holy shit, applied some pressure and it worked I love you mate, seriously thank you!
Good to know.
It helps to not support 1bit width bus modes.
Otherwise, you would have 4 times lower speeds now.
Find a flexible pad and attach it on top of the connector, so the case can keep it down.
EDIT:
I just remembered that the stock one has a pad on it. What happened to this?
Last edited by CTCaer,
I'm an idiot who threw the original one away. I put something new in it already.
I have a clean Nand that I want to restore from Hekate v3.1. I have the boot0, boot1, and rawnand.bin files.
I have also made another full backup of my Nand with Hekate 3.2 just in case the above doesn't work.
Question is there a certain order to restore the Nand files?
Also if it doesn't work can I remove the SDCard and then put my latest Hekate 3.2 Nand backup on the SD Card and then restore without powering off the Switch?
I don't want to risk a brick from occurring.
I am going to sell this switch and will ensure it is not banned before I sell it as I bought a new one with 4.1 firmware.
Thanks
I have also made another full backup of my Nand with Hekate 3.2 just in case the above doesn't work.
Question is there a certain order to restore the Nand files?
Also if it doesn't work can I remove the SDCard and then put my latest Hekate 3.2 Nand backup on the SD Card and then restore without powering off the Switch?
I don't want to risk a brick from occurring.
I am going to sell this switch and will ensure it is not banned before I sell it as I bought a new one with 4.1 firmware.
Thanks
If it's a mismatch error, that's not good; Try to run h2testw and post results.
Otherwise I'll need the error.
Nope there's no certain order. You can start from BOOT0/1 or rawnand.bin. Just make sure that you restored all of them.
Yes you can remove the sd card, as long as you are in a menu!
Otherwise you may corrupt sd card data.
But this does not matter. If the restore fails, it's still bricked. So just make sure to retry with the old or new backup again. (And don't delete any backup from your PC, until you are 100% sure.)
@CTCaer
could we compile hekate with the blob for DDR4 from Pixel C?
https://developers.google.com/android/images#ryu
with the command provided by F0:
source: https://fail0verflow.com/blog/2018/shofel2/
(I can provide the blob by PM if that can be easier for you)
could we compile hekate with the blob for DDR4 from Pixel C?
https://developers.google.com/android/images#ryu
with the command provided by F0:
Code:
./build/util/cbfstool/cbfstool bootloader-dragon-google_smaug.7900.97.0.img extract -n fallback/tegra_mtc -f tegra_mtc.bin(I can provide the blob by PM if that can be easier for you)
I have it.
The thing is why?
It's not that this will save you. You gonna still have a bottleneck from BPMP.
This could only help for backup/restore options. But still.
Edit:
Also that command does not compile it. It extracts it from pixel c coreboot.
Last edited by CTCaer,
Yes, the command is for extracting. The file is used during compilation when it is put in:
of coreboot folder.
For hekate, since it's not based on coreboot, I think it would be hardcoded to use the file.
I suggested this because of what you said yesterday:
yeah that's why I asked in the first place if we could compile hekate with this.
It seems we could but I don't know how, now.
Well this depends.
I can distribute the coreboot file even though it has this blob inside.
You can't compile it, but embed it. Good luck with that though. The blob alone exceeds the maximum payload limit.yeah that's why I asked in the first place if we could compile hekate with this.
It seems we could but I don't know how, now.
Additionally, hekate is armv4t and this blob is aarch64 and must run on the A57 cores.
So you have to enable CCPLEX and call it. Which normally do it only for horizon's secure monitor.
i don't know, maybe I'll play with this sometime. Still though, I have more important things to do (booting linux through hekate is a pain in the ass).
Similar threads
