Homebrew Alternate/Debug/Test menu working on retail 3DS

[Aletron9000]

So, I used the patched version MassExplosion213 gave us, and the update patch, however, it throws an error such as "Make sure you put the updates in '/updates'" which I did. Also, if I try to boot into Luma3ds and enable dev features and attempt to save, it will enable the patch but I have to hard reboot my console. Which then, leads to a forever black screen. I can disable and it works just fine (goes to default home menu). My config settings are only changed to enable Test Menu. Is anybody else experiencing the same problem, or is it just me. :/

I am using CakesFW, and got the same error, I got a partial downgrade though.

 

[Deleted User]

I am using CakesFW, and got the same error, I got a partial downgrade though.

Mine too. I don't think it about the partial downgrade, but SysUpdater is throwing an error about there being no app to replace the current one

 

[Aletron9000]

Mine too. I don't think it about the partial downgrade, but SysUpdater is throwing an error about there being no app to replace the current one

testing a theory that might fix this, will post if it works.

 

[Deleted User]

After it has finished, extract the firmware.bin from the firmware title (0004013800000002), and use it with luma3ds with dev features enabled

How did you extract it? All I get is an exefs unless there is someway I do not know about
Unless that is the firmware.bin

 

[Khangaroo]

Am I the only one who can't find the Panda files? I tried using every search term I can think of on that iso site and it's still not there. (also, how in the world do you extract a firmware.bin)

 

[PabloMK7]

How did you extract it? All I get is an exefs unless there is someway I do not know about
Unless that is the firmware.bin

You'll need a way to decrypt the firmware cia, then extract the contents of the exefs with ctrtool --exefsdir=folder to get the firm.bin

 

[Aletron9000]

Am I the only one who can't find the Panda files? I tried using every search term I can think of on that iso site and it's still not there. (also, how in the world do you extract a firmware.bin)

I think I found it, but those files I am trying to use to go retail to dev unit. They are still not working

 

[Deleted User]

You'll need a way to decrypt the firmware cia, then extract the contents of the exefs with ctrtool --exefsdir=folder to get the firm.bin

So, like with Asia81's tool? Because then, it gives me a code.bin

 

[PabloMK7]

So, like with Asia81's tool? Because then, it gives me a code.bin

Check it in HxD, if you read FIRM, it is the firmware file.

 

[Deleted User]

Ok

 

[Deleted member 373223]

Search on that iso site, there is a thread with all the (USA) panda titles. Then use sysupdater to install them. After it has finished, extract the firmware.bin from the firmware title (0004013800000002), and use it with luma3ds with dev features enabled. (In my case, I had to region change my nand, because I'm EUR)

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


Just supply your own DevMenu and Config titles.

What is name of thread?

 

[Aletron9000]

does anyone know how to correct the sysUpdater error when using the dev unit fw DG. I keep getting the error

fsException:
fs.cpp:177: Result: 0D8E0806A
Failed to write to file!
Did you store the update files in '/updates'?

 

[PabloMK7]

does anyone know how to correct the sysUpdater error when using the dev unit fw DG. I keep getting the error

fsException:
fs.cpp:177: Result: 0D8E0806A
Failed to write to file!
Did you store the update files in '/updates'?

Have you removed DevMenu and Config cias? You will need to supply your own. (The cias starting with 00040000)

 

[daxtsu]

does anyone know how to correct the sysUpdater error when using the dev unit fw DG. I keep getting the error

fsException:
fs.cpp:177: Result: 0D8E0806A
Failed to write to file!
Did you store the update files in '/updates'?

That error means that something had an invalid signature:
Error 0xD8E0806A
Description: Invalid signature (106)
Module: AM (32)
Summary: Invalid argument (7)
Level: Permanent (27)

So it's most likely what Pablo said.

 

[Aletron9000]

That error means that something had an invalid signature:
Error 0xD8E0806A
Description: Invalid signature (106)
Module: AM (32)
Summary: Invalid argument (7)
Level: Permanent (27)

So it's most likely what Pablo said.

But, I have CakesFW with signature patches disabled, wouldn't that make an invalid signature not matter?

 

[Svaethier]

all I did was install the cias before hand for dev and config menu then downgraded after deleting the two corrupt cias from the updates folder.

 

[daxtsu]

But, I have CakesFW with signature patches disabled, wouldn't that make an invalid signature not matter?

It can also mean the CIA was corrupted in some way.

 

[Deleted member 373223]

Can SOmebody Give me a step by step guide and the name, or at least a part, of the thread with the Panda DG pack?

 

[Aletron9000]

Have you removed DevMenu and Config cias? You will need to supply your own. (The cias starting with 00040000)

I think that might have been it, I am gonna try again. (crosses fingers)

EDIT: Success! Thanks to everyone that helped out

 

[Deleted User]

Can SOmebody Give me a step by step guide and the name, or at least a part, of the thread with the Panda DG pack?

I will make a guide soon as I have had (hopefully) a success