An issue with the Incognito help plz

[GTO]

Don’t worry about upgrading unless we can’t get it to run and hit the same errors again.

I put the file on the front of the sd card with rename it to (prodinfo.bin) and my serial number with it too (ajx123456789prodinfo.bin)
And finally (prodinfo_sysnand.bin) and still zeros in my switch.

 

[binkinator]

I put the file on the front of the sd card with rename it to (prodinfo.bin) and my serial number with it too (ajx123456789prodinfo.bin)
And finally (prodinfo_sysnand.bin) and still zeros in my switch.

Well crap. This is what @Hayato213 was worried would be the case. This backup file is a backup of the prodinfo with all zeros. If you can’t find another one and you can’t dump them from your sysnand then we are out of options and your switch is simply perma-banned.

 

[Hayato213]

I put the file on the front of the sd card with rename it to (prodinfo.bin) and my serial number with it too (ajx123456789prodinfo.bin)
And finally (prodinfo_sysnand.bin) and still zeros in my switch.

That suck to hear, unless you have a NAND backup to go back with a clean NAND you are stuck offline

 

[GTO]

That suck to hear, unless you have a NAND backup to go back with a clean NAND you are stuck offline

This is how it appears in my sd card with my full serial number in the automatic backups folder

 

[Hayato213]

This is how it appears in my sd card with my full serial number in the automatic backups folder

Sound like a backup of prodinfo after it is blank if it give you XAJ0000000000

 

[binkinator]

This is how it appears in my sd card with my full serial number in the automatic backups folder

I'm curious why the original says it cannot open the prodinfo.bin file but if that's the case we're at the end of the road.

 

[GTO]

Sound like a backup of prodinfo after it is blank if it give you XAJ0000000000

It gave me my real serial number both in the incognito rcm and in the name of the file

 

[Hayato213]

It gave me my real serial number both in the incognito rcm and in the name of the file

That kinda weird, but I have no experience using incognito RCM. I used the one Blawar created back then, proper backup give you the original serial number.

 

[GTO]

That kinda weird, but I have no experience using incognito RCM. I used the one Blawar created back then, proper backup give you the original serial number.

I actually don't know if the cfw build in the sd card or the switch it self do you guys recommend that I format it with haku33 and it maybe will be in ofw

 

[linuxares]

oh dear oh dear, never use Incognito. Use the inbuilt thing in Atmosphere.

 

[GTO]

I'm actually blanking my serial number just in case someone can stole it (I don't know if that's even possible but just in case) under it is my real serial number

 

[binkinator]

I actually don't know if the cfw build in the sd card or the switch it self do you guys recommend that I format it with haku33 and it maybe will be in ofw

So hold on...let's look at what's happening here.

I_RCM reads your bis_keys and then states that your serial number is XAJ700053XXX

I think it might be getting this from your actual sysnand.

When you boot up without CFW does it show your correct Serial?

 

[GTO]

So hold on...let's look at what's happening here.

I_RCM reads your bis_keys and then states that your serial number is XAJ700053XXX

I think it might be getting this from your actual sysnand.

When you boot up without CFW does it show your correct Serial?

I actually don't know how to boot into ofw cuz it is a mess what i did but those xxx I blanked it just in case someone can stole it

 

[binkinator]

I actually don't know how to boot into ofw cuz it is a mess what i did but those xxx I blanked it just in case someone can stole it

Boot without injecting anything. If you don't know how to do that please post your hekate_ipl.ini and we'll see if you have an entry we can use.

 

[GTO]

Boot without injecting anything. If you don't know how to do that please post your hekate_ipl.ini and we'll see if you have an entry we can use.

This what I got when I try to boot to stook through hekate. Where can I find hekate_ipl.ini please

 

[GTO]

This is it

 

[GTO]

Someone tell me that it's most likely atmosphere config blanking it out because it's show in the incognito rcm my real serial number. I actually don't know if using haku33 would fix it.

 

[binkinator]

This what I got when I try to boot to stook through hekate. Where can I find hekate_ipl.ini please

Look under sd:/bootloader/hekate_ipl.ini

This is it

we should be able to see how it's pointing to thk.bin (not what we need) in the hekate_ipl.ini file that you get from above.

thk.bin is part of the Hekat/nyx package (had to look it up). Once we get you sorted you should probably upgrade everything but let’s hold off on that for now.

bootloader/
├── hekate_ipl.ini
├── ini
├── nyx.ini
├── patches.ini
├── payloads
│ ├── fusee.bin
│ ├── hekate_ctcaer_5.6.0.bin
│ └── Lockpick_RCM.bin
├── res
│ ├── icon_payload.bmp
│ └── icon_switch.bmp
├── sys
│ ├── emummc.kipm
│ ├── libsys_lp0.bso
│ ├── libsys_minerva.bso
│ ├── nyx.bin
│ ├── res.pak
│ └── thk.bin
└── update.bin

Someone tell me that it's most likely atmosphere config blanking it out because it's show in the incognito rcm my real serial number. I actually don't know if using haku33 would fix it.

It could very well be atmosphere. share your /atmosphere/config/exosphere.ini file as well.

We're interested in these lines but paste the whole thing just in case:

blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=0

If things are broken, running haku33 is not going to fix them. Let's find out for sure what's going on. Hang tight.

 

[GTO]

Somone in reddit tells me that i was using exosphere with out even knowing and he was right so thanks to him I was able to restore my serial number back. I want to thank you all for trying to help and special thanks to binkinator and hayato213 I'm really grateful for you both thanks.

 

[GTO]

Look under sd:/bootloader/hekate_ipl.ini



we should be able to see how it's pointing to thk.bin (not what we need) in the hekate_ipl.ini file that you get from above.

thk.bin is part of the Hekat/nyx package (had to look it up). Once we get you sorted you should probably upgrade everything but let’s hold off on that for now.

bootloader/
├── hekate_ipl.ini
├── ini
├── nyx.ini
├── patches.ini
├── payloads
│ ├── fusee.bin
│ ├── hekate_ctcaer_5.6.0.bin
│ └── Lockpick_RCM.bin
├── res
│ ├── icon_payload.bmp
│ └── icon_switch.bmp
├── sys
│ ├── emummc.kipm
│ ├── libsys_lp0.bso
│ ├── libsys_minerva.bso
│ ├── nyx.bin
│ ├── res.pak
│ └── thk.bin
└── update.bin


It could very well be atmosphere. share your /atmosphere/config/exosphere.ini file as well.

We're interested in these lines but paste the whole thing just in case:

blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=0

If things are broken, running haku33 is not going to fix them. Let's find out for sure what's going on. Hang tight.

Thank you I mean it