Hacking Question Burnt 8 fuses and tried to use Backup NAND that was 5.1.0 now getting blue screen

[LegendAssassinF]

I found out the issue to my previous thread I am trying to boot into a previous firmware so how do I update to the latest firmware? I have access to any payload but not sure what to use or how to use them

 

[Lumince]

Do you have AutoRCM installed?
Did you restore boot0 and boot1 as well?

You could restore a backup (if you made one) from before you tried to downgrade? If not, you could probably use the PC version of choidujournx.

 

[syntaxyz]

Follow this guide from rajkosto,
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

 

[LegendAssassinF]

Follow this guide from rajkosto,
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Awesome I'll do this tonight I just dont get what happened lol

 

[Lumince]

Awesome I'll do this tonight I just dont get what happened lol

did you restore your boot0/1 backups??? if so it wont boot lol

 

[LegendAssassinF]

did you restore your boot0/1 backups??? if so it wont boot lol

I dont have a boot0/1 I missed backing them up previously. Is there anyway to get another boot0/1

 

[Lumince]

I dont have a boot0/1 I missed backing them up previously. Is there anyway to get another boot0/1

nope.... time to update using that link then lol

 

[LegendAssassinF]

nope.... time to update using that link then lol

What link? I want to get to 6.2.0 anyway

 

[LegendAssassinF]

Follow this guide from rajkosto,
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

I'm not sure how to get the prod.keys? I am not able to run any homebrew so not sure how to obtain them.

 

[syntaxyz]

Have you trted dumping the keys with this?
https://github.com/rajkosto/biskeydump

 

[LegendAssassinF]

Have you trted dumping the keys with this?
https://github.com/rajkosto/biskeydump

Yes and I ended up with the device.keys..... oh wait is that prod.keys if I just rename it?

 

[syntaxyz]

I honestly havent kept up with this part of the scene enough to know if there are now different formats used for the key file. I see different file extentions floating around for this (ini, txt ,.keys). Maybe you are better off downloading a prod.keys template somewhere and fix it yourself.
Good luck

 

[LegendAssassinF]

I honestly havent kept up with this part of the scene enough to know if there are now different formats used for the key file. I see different file extentions floating around for this (ini, txt ,.keys). Maybe you are better off downloading a prod.keys template somewhere and fix it yourself.
Good luck

Damn well thanks anyway Been trying to fix this, I just wish it was possible to just get into the original firmware into recovery and I'll just go to 6.2.0, I think trying to use a RawNAND.bin for 5.1.0 broke everything but allowing me to run payloads.

 

[Scarlet]

nope.... time to update using that link then lol

For what it's worth, you can generate new ones. If the boots are the only thing missing from a backup, it's entirely salvageable.

 

[LegendAssassinF]

For what it's worth, you can generate new ones. If the boots are the only thing missing from a backup, it's entirely salvageable.

How would I go about that? Currently trying to do the "How to install/run" guide but now stuck on obtaining prod.keys lol If it isn't one thing it is another it seems

 

[Scarlet]

How would I go about that? Currently trying to do the "How to install/run" guide but now stuck on obtaining prod.keys lol If it isn't one thing it is another it seems

I ran through the choi guide and used the firmware files of my nand backup firmware (2.3.0 update files to match the 2.3.0 backup). You only need to follow it up until restoring the boot0/boot1 parts, and your previously-failing backup should now boot.

 

[LegendAssassinF]

I ran through the choi guide and used the firmware files of my nand backup firmware (2.3.0 update files to match the 2.3.0 backup). You only need to follow it up until restoring the boot0/boot1 parts, and your previously-failing backup should now boot.

ok I'll give that a try. I am still not sure how to obtain my keys.txt file though which is the current issue. I can't boot any CFW so not sure how to obtain it. I tried downloading but it just fails to match anything.

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

I ran through the choi guide and used the firmware files of my nand backup firmware (2.3.0 update files to match the 2.3.0 backup). You only need to follow it up until restoring the boot0/boot1 parts, and your previously-failing backup should now boot.

Yeah the same issue it requires prod.keys and I'm not sure how to obtain those.

 

[LegendAssassinF]

I ran through the choi guide and used the firmware files of my nand backup firmware (2.3.0 update files to match the 2.3.0 backup). You only need to follow it up until restoring the boot0/boot1 parts, and your previously-failing backup should now boot.

Little update I was able to continue by getting keys.txt online somewhere, deleted everything I didn't need so currently working on step 8 part

 

[Shadowhand]

Little update I was able to continue by getting keys.txt online somewhere, deleted everything I didn't need so currently working on step 8 part

You don't have to do any of that. Use hekate to boot your 5.1, and update with ChoiDujourNX

 

[LegendAssassinF]

You don't have to do any of that. Use hekate to boot your 5.1, and update with ChoiDujourNX

How would I do that? In the options I can hit boot normal and it just black screens. I can't get beyond a black screen or a blue screen with anything I do