Hacking [Release] PBT-CFW - Import CIAs on your SYSNAND

[nop90]

Install a sys update different from the browser with this tool, and you'll propably brick the 3DS.

If you want to experiment, use a hard modded 3DS so you can restore your nand if it bricks.

 

[b17bomber]

I did find out that Zelda Four Swords Adventures when installed to a CFW boots just fine. So there is that

I assume scene ambassador GBA games won't work with this either, right?

 

[laharl22]

How to install this cfw over palantine?

 

[Cyan]

You can install any cia directly with palantine's ctrclient?
I always thought that it would require to install devmenu first, then install the browser title, because that's what every body is doing.
But I can install the browser title directly on my sysnand without using a leaked sdk file.


I just need to put all palantines files to SD, your boot.bin and that's all.
Launching gateway exploit will allow cia install on SysNAND, then use ctrclient to send the browser.

users reported that using ctrclient is not always successful, they had to try and reboot their emuNAND multiple times.
Is it an emuNAND redirection issue, or does it happen on sysNAND too?
I wouldn't want to install cia on sysNAND and fail midway because of instability.

Edit:
Well, that ends my questions. ctrclient.exe from palantine doesn't work on WinXP 32bit...
so, I can't use that method
I guess if nobody has a 32bit version my only solution is devmen/brm from gateway.
there's so many users on 64bit now? I feel like the last 32bit user

 

[JaapDaniels]

it's preinstalled with latest cfw.

 

[Cyan]

How to install this cfw over palantine?

just replace the boot.bin file on your SD card.
it will not redirect NAND to emuNAND and everything will be done on your sysNAND.


I still don't like the word "custom firmware" as it's not one. you don't replace your firmware at console's boot, you only launch a homebrew to patch files.

 

[nop90]

I still don't like the word "custom firmware" as it's not one. you don't replace your firmware at console's boot, you only launch a homebrew to patch files.

I agree, but when in the past i used different names, a lot of people misuderstood and started a never ending loop of nonsense "so if I do this ... maybe I could obtain that ...". I'm hoping that KARL will clean this bad habit .

users reported that using ctrclient is not always successful, they had to try and reboot their emuNAND multiple times.
Is it an emuNAND redirection issue, or does it happen on sysNAND too?

Same issues. But strangely I found this patch a lot more stable while in CTRsrv mode (booting with L Key pressed).

I wouldn't want to install cia on sysNAND and fail midway because of instability.

Installing only the browser should not be daungerous. If it fails, the browser wont start, but your FIRM will nor be bricked. So you can still do a new install. For other firmware updates a connection interruption could be potentially a disaster. The same of turning off the 3DS (or any other device) during system update.

Instead of devmenu you can install Big Red Menu. You will wait a little more, but it works.

 

[mid-kid]

-

Oh fuck yes.
Now I can install my 3DSWare on sysNAND without having to use a dual emuNAND.
...and legit CIAs without fucking around with ticket.db.

 

[Kakkoii]

You can install any cia directly with palantine's ctrclient?
I always thought that it would require to install devmenu first, then install the browser title, because that's what every body is doing.
But I can install the browser title directly on my sysnand without using a leaked sdk file.


I just need to put all palantines files to SD, your boot.bin and that's all.
Launching gateway exploit will allow cia install on SysNAND, then use ctrclient to send the browser.

users reported that using ctrclient is not always successful, they had to try and reboot their emuNAND multiple times.
Is it an emuNAND redirection issue, or does it happen on sysNAND too?
I wouldn't want to install cia on sysNAND and fail midway because of instability.

Edit:
Well, that ends my questions. ctrclient.exe from palantine doesn't work on WinXP 32bit...
so, I can't use that method
I guess if nobody has a 32bit version my only solution is devmen/brm from gateway.
there's so many users on 64bit now? I feel like the last 32bit user

Yes... Because there's absolutely no reason to stay on 32bit. 32bit restricts you to 4GB of system RAM usage, and has worse performance than 64bit. Is your CPU not capable of 64bit? If it is, then get your ass onto Windows 7 already, or even 8/10

 

[MrCheeze]

So, if I unthinkingly followed a guide's advice and formatted my sysnand to unlink it from emunand/cfw, this is useless to me, right?

 

[dubbz82]

How to install this cfw over palantine?

If you have to ask this, this probably isn't for you.

 

[bannana2]

If you have to ask this, this probably isn't for you.

sorry, but that statement made to whomever you intended is not logical or rational.

If you have to ask this, this probably isn't for you.

if you c

 

[Relys]

I still don't like the word "custom firmware" as it's not one. you don't replace your firmware at console's boot, you only launch a homebrew to patch files.

This is a chain of multiple exploits to gain full control over the system, load a modified (i.e. "custom") FIRM image (yes, the magic header is even called FIRM) and then soft reboot the system. It is literally, by definition, "custom firmware". Gaining an entry point during the systems initial boot (as opposed to when we gain access during a soft reboot) just enables automated persistence. boothax is a matter of convenience and does not change the definition or the overall rest of the process.

 

[MrDaveIsAwesome]

Is this any more stable then Palantine's CFW, cause that one only boots like 1 out of every 5 attempts

 

[Oishikatta]

Is this any more stable then Palantine's CFW, cause that one only boots like 1 out of every 5 attempts

It's just an edit of the same thing, as said in the first line of the post.

 

[MrDaveIsAwesome]

K thanks, I assumed that but just making sure

 

[Zidapi]

This is a chain of multiple exploits to gain full control over the system, load a modified (i.e. "custom") FIRM image (yes, the magic header is even called FIRM) and then soft reboot the system. It is literally, by definition, "custom firmware". Gaining an entry point during the systems initial boot (as opposed to when we gain access during a soft reboot) just enables automated persistence. boothax is a matter of convenience and does not change the definition or the overall rest of the process.

Relys sure knows how to make a point. Well, that settles that.

I hope this puts end to that "but it's not a CFW unless it loads at boot" bullshit.

 

[Cyan]

Ok, it's a modified FIRM title.
But I'm on the impression users think that redirecting the eMMC (EmuNAND, redNAND, etc.) is what is called a custom firmware.
thinking that being on emuNAND is being on a Custom firmware.

You look at the FIRM patching process, I looked at the results, what users have access to and that they are calling custom firmware (which is a copy of their system, not a custom one).
users usually call the full system file the "firmware". "I'm at firmware 9.2.0 !" which is NOT the firmware.
like you said, the firmware is only a file (which has FIRM in the header)

just a different point of view I guess.

 

[Heran Bago]

Q: Is it possible ...
A: No

Really cool thing you got going but I have to correct you here. Anything is possible if you believe in yourself.

 

[nop90]

I edited that post right now.

That DSWare cia works in emunand too with Palantine CFW. So there is nothing strange if it works in Sysnand with sign check removed.