I did find out that Zelda Four Swords Adventures when installed to a CFW boots just fine. So there is that
just replace the boot.bin file on your SD card.How to install this cfw over palantine?
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.
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.
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
How to install this cfw over palantine?
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 cIf you have to ask this, this probably isn't for you.
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.
Is this any more stable then Palantine's CFW, cause that one only boots like 1 out of every 5 attempts
Relys sure knows how to make a point. Well, that settles that.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.
Q: Is it possible ...
A: No