Hacking Boot0 or boot1 won't mount to pc through hekate

[linuxares]

Formatting the sd is not needed but merging old atmosphere version with new ones can be a problem. I suggest you delete all files and folders except a Nintendo and Emunand folder (if they exist) and then paste the deepsea files and use the included hekate payload

Post automatically merged: Feb 26, 2024

Then we go from there. But we need to make sure that we fix one problem at a time instead of aimlessly trying a lot of things

Any idea? I honestly think it's a semi-dead APU.

What does this say?

• Using the VOL and Power buttons to navigate, select Console info...
• Select Print fuse info (not kfuse info).
• Press Power to save fuse info to SD card.
• Select Print TSEC keys.
• Press Power to save TSEC keys to SD card.

 

[Slluxx]

Any idea? I honestly think it's a semi-dead APU.

What does this say?

• Using the VOL and Power buttons to navigate, select Console info...
• Select Print fuse info (not kfuse info).
• Press Power to save fuse info to SD card.
• Select Print TSEC keys.
• Press Power to save TSEC keys to SD card.

I am not sure. but i wonder if its possible to go into maintenance mode (holding vol - and vol + while pressing power once).

 

[GreenDuck65777]

Any idea? I honestly think it's a semi-dead APU.

What does this say?

• Using the VOL and Power buttons to navigate, select Console info...
• Select Print fuse info (not kfuse info).
• Press Power to save fuse info to SD card.
• Select Print TSEC keys.
• Press Power to save TSEC keys to SD card.

You mean this?

Post automatically merged: Feb 26, 2024

I am not sure. but i wonder if its possible to go into maintenance mode (holding vol - and vol + while pressing power once).

I need to turn it completely off and try press vol - and vol + and power once?

 

[linuxares]

You mean this?

Post automatically merged: Feb 26, 2024

I need to turn it completely off and try press vol - and vol + and power once?

Press "Dump fuses" on the second screen

 

[GreenDuck65777]

Press "Dump fuses" on the second screen

What next?

 

[Slluxx]

I need to turn it completely off and try press vol - and vol + and power once?

turn off, hold vol +/- and keep it held while pressing power once.

 

[linuxares]

What next?

CAL0 info does it show anything?

Try what @Slluxx recommended first however

 

[GreenDuck65777]

CAL0 info does it show anything?

Try what @Slluxx recommended first however

Cal0 kinda broken

 

[linuxares]

Cal0 kinda broken

Figured, well turn switch off via Hekate and do "maintenance mode (holding vol - and vol + while pressing power once)."

 

[GreenDuck65777]

Also maintenance mode not working. It's just not booting up. Black screen and that's it.

 

[Slluxx]

Cal0 is basically prodinfo content. I dont know how one can detroy this other than mounting something that shouldnt be mounted and messing with it or using Incognito or something like it.

How do you know that your nand backup is broken too? I find it hard to believe, especially if you did the backup before messing with things.

 

[GreenDuck65777]

Cal0 is basically prodinfo content. I dont know how one can detroy this other than mounting something that shouldnt be mounted and messing with it or using Incognito or something like it.

How do you know that your nand backup is broken too? I find it hard to believe, especially if you did the backup before messing with things.

I made it after messing with things. Maybe somewhere I misstyped.

 

[linuxares]

for me this sounds like a need for a donor nand. It sounds like a faulty emmc or somehow got corrupted.

 

[Slluxx]

Well, with your prodinfo gone, the only thing thats left for you (if you are out of good backups) is trying to get/generate a generic one.
https://github.com/CaramelDunes/prodinfo_gen

HOWEVER This might only be the first issue of a long list. If more than the prodinfo is gone/broken, is unlikely that you will ever fix your switch and indeed need a new one. Probably the cheapest way is to get a mangled one with a broken screen and rip the motherboard out. But thats something for later to worry about. You should try generating a prodinfo and see if that makes your switch boot.

 

[GreenDuck65777]

for me this sounds like a need for a donor nand. It sounds like a faulty emmc or somehow got corrupted.

I don't think that it's faulty. It's showing in hekate like a normal one.

Post automatically merged: Feb 26, 2024

Well, with your prodinfo gone, the only thing thats left for you (if you are out of good backups) is trying to get/generate a generic one.
https://github.com/CaramelDunes/prodinfo_gen

So, my prodinfo just deleted itself?

 

[Slluxx]

I don't think that it's faulty. It's showing in hekate like a normal one.

Post automatically merged: Feb 26, 2024

So, my prodinfo just deleted itself?

No. Its usererror. You did something that broke it. Either by mounting something that shouldnt be mounted, running a bricker payload or whatever. Maybe something failed with a tegraexplorer script. I dont know. But it for sure happend because you did something

 

[linuxares]

I don't think that it's faulty. It's showing in hekate like a normal one.

Well something wiped your NAND and your keys can't get generated.

 

[GreenDuck65777]

Well, with your prodinfo gone, the only thing thats left for you (if you are out of good backups) is trying to get/generate a generic one.
https://github.com/CaramelDunes/prodinfo_gen

HOWEVER This might only be the first issue of a long list. If more than the prodinfo is gone/broken, is unlikely that you will ever fix your switch and indeed need a new one. Probably the cheapest way is to get a mangled one with a broken screen and rip the motherboard out. But thats something for later to worry about. You should try generating a prodinfo and see if that makes your switch boot.

I already want to cry
Okay, this is fine. I can handle it.

 

[linuxares]

Well, with your prodinfo gone, the only thing thats left for you (if you are out of good backups) is trying to get/generate a generic one.
https://github.com/CaramelDunes/prodinfo_gen

HOWEVER This might only be the first issue of a long list. If more than the prodinfo is gone/broken, is unlikely that you will ever fix your switch and indeed need a new one. Probably the cheapest way is to get a mangled one with a broken screen and rip the motherboard out. But thats something for later to worry about. You should try generating a prodinfo and see if that makes your switch boot.

btw that one doesn't work for 17+

 

[Hayato213]

https://gbatemp.net/threads/am-i-broke-format-on-mmc-chip-and-is-this-even-possible-to-fix.647844/

Probably he did this broke it.