Homebrew (help!) 3dsident shows n3ds kernel/firm 2.52-0 AFTER dgtools nfirm flash?

[jaderocc]

title says it all.. i am using the dsiware downgrade method to go from 11.2 to 9.2. i'm at step 9 where you are told - "3. Select “Downgrade FIRM to 10.4” and confirm to flash the 10.4.0 NFIRM bin to the target 3DS"

after this it says to check in 3dsident and when i do so it tells me i am still on kernel + firm 2.52-0. i have tried using both firm111_NEW.bin and firm112_NEW.bin with the firm104_NEW.bin from the corresponding folders, placed into the dgTools folder on the root of my sd card. i had an older version of dgtools and updated it to 2.0.0, and am still getting the same error. i have seen two other people with this error and their problems were solved by using the 111_NEW.bin file, however that hasn't changed anything for me. when i dgtools flash to 10.4, reboot, then come back into 3dsident once the 3ds has booted fully i still get 2.52-0... does anybody have any idea what i could be doing wrong?

 

[zoogie]

Try it with firm110_NEW.bin and firm104_NEW.bin.

 

[jaderocc]

tried that a minute after making this post, still 2.52-0

 

[zoogie]

tried that a minute after making this post, still 2.52-0

Is your firm104_NEW.bin file 4MB?

 

[jaderocc]

Is your firm104_NEW.bin file 4MB?

yep, specifically 4.096mb

 

[zoogie]

yep, specifically 4.096mb

This is just wild guesswork, but try this
https://www.3dbrew.org/wiki/Recovery_Mode
and just turn off your 3ds.

Then go to system settings -> update and "update" (i know your on latest firm).
Then try dgtool again with firm112... etc.
I suspect your firm0 is corrupt and that might trigger it to be repaired. dgtool only writes to firm0 so it needs a clean firm there for the known plaintext thing to work.

 

[jaderocc]

This is just wild guesswork, but try this
https://www.3dbrew.org/wiki/Recovery_Mode
and just turn off your 3ds.

Then go to system settings -> update and "update" (i know your on latest firm).
Then try dgtool again with firm112... etc.
I suspect your firm0 is corrupt and that might trigger it to be repaired. dgtool only writes to firm0 so it needs a clean firm there for the known plaintext thing to work.

so that went through using the firm112_NEW and i'm now on 2.51-2. going to try with firm111 and see if that takes me down to where i need to be

--------------------- MERGED ---------------------------

so that went through using the firm112_NEW and i'm now on 2.51-2. going to try with firm111 and see if that takes me down to where i need to be

okay, so after trying to use firm111 3dsident tells me i am on 2.52-0 again...

 

[zoogie]

so that went through using the firm112_NEW and i'm now on 2.51-2. going to try with firm111 and see if that takes me down to where i need to be

--------------------- MERGED ---------------------------


okay, so after trying to use firm111 3dsident tells me i am on 2.52-0 again...

I guess try firm112 again. This really confuses me
I think your 3ds is a troll.

 

[jaderocc]

it really is... i'm not sure if it makes a difference but this is the new 3dsxl that came out last month, the black pokemon sun/moon one with solgaleo/lunala.. have now tried every combination of files (110-112 with different 104 firm files) as well as older versions of boot.nds to see if that would do it, and i'm still getting 2.52-0 most of the time when i boot. the times i've gotten 2.51-2 i've tried switching the 111 file with the 110 file and it just returns back to 2.52.0... this is kind of ridiculous lol

 

[jaderocc]

reinstalled boot.nds 2.0.0 from plailect's github and 112_NEW/104_NEW and am getting 2.52-0 again.. bruv

 

[Joel16]

reinstalled boot.nds 2.0.0 from plailect's github and 112_NEW/104_NEW and am getting 2.52-0 again.. bruv

Just to make sure the latest release didn't break anything. Can you try with 3DSident v0.6.1 https://github.com/joel16/3DSident/releases/tag/0.6.1
Because I don't normally test things with homebrew loader anymore, and so something might have broken up. It's probably not going to solve your issue, but just want to make sure both versions give the same result, because the latest version did go through some code refactoring.

 

[jaderocc]

Just to make sure the latest release didn't break anything. Can you try with 3DSident v0.6.1 https://github.com/joel16/3DSident/releases/tag/0.6.1
Because I don't normally test things with homebrew loader anymore, and so something might have broken up. It's probably not going to solve your issue, but just want to make sure both versions give the same result, because the latest version did go through some code refactoring.

thanks for the response - tried it on 0.61, still getting the same reads.

 

[Joel16]

thanks for the response - tried it on 0.61, still getting the same reads.

Thanks just wanted to confirm that the code refactoring didn't much up anything for HBL.

 

[zoogie]

thanks for the response - tried it on 0.61, still getting the same reads.

If you ever get 2.51-2 again, I would dump a F0F1_new3ds.bin backup of that since it will work with slowhax when it's released.

 

[jaderocc]

If you ever get 2.51-2 again, I would dump a F0F1_new3ds.bin backup of that since it will work with slowhax when it's released.

thanks, i'll keep this in mind. appreciate yall tryna help me out of this weird situation lol. i'll post if i figure it out so if anyone has a similar problem it can hopefully help them out 2 :^)

 

[Kevin_Hawke]

I was having the same problem and managed to fix it just now - the difference is, I'm on an old 3DS. Still, this might help! The post that helped me out was this...

"I figured it out, If you have an issue with Kernel or FIRM version of 2.51-2 you have to run the 11.1 and 10.4 downgrade until you get 2.51-0, then you redo the dgTools with the 11.0 compatible version. You then exchange the 11.1 to 11.0 and redo the downgrade to 10.4 this will take you down to Kernel and/or FIRM version of 2.50-11 and now you can downgrade the firmware to 9.2. I got it to work"

Basically, when I used the 11.2 downgrader, it got me to 2.51-0. After that, I used the 11.0 downgrader and it got me to 2.50-11! Hope this helps you, bud.

 

[chaos7738]

Dear all
I having the same problem, i am still on kernel and firm @ 2.52-0.
i am on ver 11.2 new 3ds. i had try all firm yet still @ 2.52-0.
some question:
Do i need to Dump f0f1 every time i try on firm11x_NEW.bin and firm104_NEW.bin?
when the dump come out a new F0F1_NEW3DS file. do i just leave it on the folder or i need to put somewhere else?
If i try other firm do i need to delete this F0F1_NEW3DS files?
Do i need to restore any nand?

Thanks for the help

 

[Roomsaver]

Dear all
I having the same problem, i am still on kernel and firm @ 2.52-0.
i am on ver 11.2 new 3ds. i had try all firm yet still @ 2.52-0.
some question:
Do i need to Dump f0f1 every time i try on firm11x_NEW.bin and firm104_NEW.bin?
when the dump come out a new F0F1_NEW3DS file. do i just leave it on the folder or i need to put somewhere else?
If i try other firm do i need to delete this F0F1_NEW3DS files?
Do i need to restore any nand?

Thanks for the help

You only need to dump your firm once, unless the dump was corrupted or something like that. You can leave it in the folder but since it's your NFIRM backup you should probably back it up somewhere.

 

[chaos7738]

You only need to dump your firm once, unless the dump was corrupted or something like that. You can leave it in the folder but since it's your NFIRM backup you should probably back it up somewhere.

Thanks for the help. I just figure and sone the downgrade a moment ago.i start from 11.2 >11.1>11.0>11.1 and finally get it.but now i newd a qr Qr code to login to browserhax. Which browser QR still working now?

 

[Roomsaver]

I don't think mtheall is up right now. You'll either have to wait or use another entrypoint.