Hacking Why does no CFW support 2.1 EmuNAND?

[Zan']

I am not really into CFW developing.
I would like to get into it though and lestn about it. I know there are differences in the FIRM that need to be accounted for and things like that.
I believe I understood how it was made possible to fix a 2.1 "bricked" NAND for new3DS.
But why exactly does no CFW support 2.1 EmuNAND?
What would be needed to get it running and where are the difficulties?
It would be really helpful and a lot safer to get the 2.1FW running on emuNAND to dump the OTP.
And if the EmuNAND was partially running (not perfectly but loading) 2.1 would it even be possible to get the OTP?

 

[Deleted member 370671]

The question here should be "Why would a CFW support 2.1?"

It's useless, except maybe for debugging or something like that

EDIT: And actually, I don't think it would be possible to get the OTP with a 2.1 emuNAND, since the system already locked the access to it.

 

[Zan']

The question here should be "Why would a CFW support 2.1?"

It's useless, except maybe for debugging or something like that

EDIT: And actually, I don't think it would be possible to get the OTP with a 2.1 emuNAND, since the system already locked the access to it.

I guess if you want to do so to dump the OTP you would have to run the emuNAND from some other way than direct boot.
That would possibly not give you access to the OTP part again. So I expect it's not possible. But I don't know for sure.
It might if you run it from A9LH (not that you don't already have the OTP then)

I would still like to know what is keeping cfw from supporting 2 1

 

[Supster131]

Like @TheKawaiiDesu stated, it's not possible to dump the OTP from emuNAND, even if a CFW supported it.

As for why CFWs don't support 2.1, afaik, it's really different compared to 3.0+, so it would take a lot of work to get it working. Not only that, but OTPHelper can tell you if your emuNAND downgraded properly and if it's bricked or not, so there isn't really a point in working on a CFW that supports 2.1 anymore.

 

[Froster]

I don't understand why but it will somehow take a lot of work

(Hey look I'm officially a member )

 

[Zan']

Like @TheKawaiiDesu stated, it's not possible to dump the OTP from emuNAND, even if a CFW supported it.

As for why CFWs don't support 2.1, afaik, it's really different compared to 3.0+, so it would take a lot of work to get it working. Not only that, but OTPHelper can tell you if your emuNAND downgraded properly and if it's bricked or not, so there isn't really a point in working on a CFW that supports 2.1 anymore.

Thanks.
Well I forgot that a validation method for the 2.1 NAND was introduced.
So it wouldn't really help you with the OTP. Just to play around.
If there were ways to get access to the OTP again on a different way you wouldn't need the 2.1 NAND either way.

 

[Supster131]

Tha

Thanks.
Well I forgot that a validation method for the 2.1 NAND was introduced.
So it wouldn't really help you with the OTP. Just to play around.
If there were ways to get access to the OTP again on a different way you wouldn't need the 2.1 NAND either way.

That is very unlikely though, as OTP is locked upon boot in firmwares 3.0+. 2.1 was the last firmware to not lock the OTP.

 

[Deleted member 370671]

Thanks.
Well I forgot that a validation method for the 2.1 NAND was introduced.
So it wouldn't really help you with the OTP. Just to play around.
If there were ways to get access to the OTP again on a different way you wouldn't need the 2.1 NAND either way.

Well, this should be impossible unfortunately, since the OTP is locked long before the OS is even loaded (and long before we can run code), and we can't unlock it. If Nintendo didn't forget to lock the OTP on 2.1, we wouldn't have A9LH.

 

[Zan']

That is very unlikely though, as OTP is locked upon boot in firmwares 3.0+. 2.1 was the last firmware to not lock the OTP.

Well, this should be impossible unfortunately, since the OTP is locked long before the OS is even loaded (and long before we can run code), and we can't unlock it. If Nintendo didn't forget to lock the OTP on 2.1, we wouldn't have A9LH.

I was just trying to say that if you would be able to unlock the OTP again there wouldn't be a reason for 2.1
Therefore a 2.1 cfw would be (even if you could unlock the OTP again) still kinda useless to actually get the OTP.
I wasn't trying to say it would (ever) be possible or that I was hoping for it.
I don't have a need to dump my OTP anymore since I have it already.
And I got my answer to the question what's keeping cfw from running 2.1

 

[astronautlevel]

Well, this should be impossible unfortunately, since the OTP is locked long before the OS is even loaded (and long before we can run code), and we can't unlock it. If Nintendo didn't forget to lock the OTP on 2.1, we wouldn't have A9LH.

Theoretically, if we ever discovered an exploit in the bootrom (but don't count on it, we haven't dumped bootrom yet) we could theoretically run code during the stages of the bootrom which would theoretically allow us to dump OTP on any firmware.

But there's a reason I said "theoretically" about five times in my post.

 

[raulpica]

Closed by OP request.