Hacking How to fix black screen rxTools boot

[wurstpistole]

The firmware is not longer in the archive, thus rendering the whole idea useless. If people used the wrong firmware before, they will also use the wrong firmware now and things still won't work. Please just delete this thread

 

[subcon959]

Yeah, that's how I know he doesn't know what he's talking about. Those 2 files are not even used for this version of rxtools. The actual firmware files are in the folder called firm. Which you are supposed to generate yourself with the provided python script as it's copyrighted material.

 

[Viris]

It works because its basically a warez package.

I don't like calling people out that are trying to be helpful, but look at the fact that it says to copy rxtools.dat to the SD. The boot entry for rxtools (that he edited to include his name) calls code.bin not rxtools.dat :-/

Many people fail to install rxtools 3.0 properly,and this leads to a black screen when you try to start it with ctrbootmanager.With this guide I try so simple and clear,to accommodate the installation of rxtools,to enable people to use ctrbootmanager.


Many people do not know how to install it . I tried to make life easier for everyone, giving available folders ready to insert the SD . So as to avoid unnecessary steps as replacing files etc .. I put the name because the job of " simplification " I did it is a kind of credits . So do not be an idiot and try to help you people , if you feel so great ; )

 

[TheDuckMan64]

The firmware is not longer in the archive, thus rendering the whole idea useless. If people used the wrong firmware before, they will also use the wrong firmware now and things still won't work. Please just delete this thread

Actually, no it is not. If @Viris just links to a pastebin, and reuploads the firmware.bin and slotKeywhatever.bin, this thread would be perfect for noobs/ people who are absolutely stumped. So don't delete it.

Yeah, that's how I know he doesn't know what he's talking about. Those 2 files are not even used for this version of rxtools. The actual firmware files are in the folder called firm. Which you are supposed to generate yourself with the provided python script as it's copyrighted material.

If he doesn't know what he's talking about then why does his tutorial work? Only plebs fight over the measly 3-4mb lost to those 2 files. I also have yet to see another tut that fixes this black screen issue.

 

[subcon959]

As I already said it works because it includes the COPYRIGHTED firmware files. It's a warez package not a tutorial. In case you were confused.. this isn't that iso site. THAT is the only issue here.

 

[TheDuckMan64]

As I already said it works because it includes the COPYRIGHTED firmware files. It's a warez package not a tutorial. In case you were confused.. this isn't that iso site. THAT is the only issue here.

Check my previous posts, dumbass. Nothing illegal about linking to a pastebin.

 

[wurstpistole]

Check my previous posts, dumbass. Nothing illegal about linking to a pastebin.

Keep your insults down. He decided to ignore my advice to link to a pastebin and just removed all the files, especially the firmware file which for some reason most of the people have problems in acquiring the right one for their device.
Actually it's so easy. O3DS uses python script, N3DS uses 9.5 encrypted file. Done. No more rxTools problems.

In fact I see the bigger problem here to provide a very old rxTools version (no nightly in the last months used a dat file to launch).

 

[subcon959]

Check my previous posts, dumbass. Nothing illegal about linking to a pastebin.

OH FFS.. ok I'll try to make it clear to you. The archive contains an rxtools folder. The rxtools folder contains a firm folder. The firm folder contains 3 COPYRIGHTED firmware files. They are still there RIGHT NOW. Feel free to download it again and look for yourself.

The 2 files that you and wurst were talking about that he deleted have nothing to do with this discussion OR this particular rxtools release for that matter.

CHRIST my friggin 6 yr old can follow things with more intelligence.

 

[TheDuckMan64]

OH FFS.. ok I'll try to make it clear to you. The archive contains an rxtools folder. The rxtools folder contains a firm folder. The firm folder contains 3 COPYRIGHTED firmware files. They are still there RIGHT NOW. Feel free to download it again and look for yourself.

The 2 files that you and wurst were talking about that he deleted have nothing to do with this discussion OR this particular rxtools release for that matter.

CHRIST my friggin 6 yr old can follow things with more intelligence, like that fella with the candy and the pretty van

My sd has no firm folder, I'm using firmware.bin, as rxTools 3.0 can support both I believe. Pretty smart 6 year old ya got there though

EDIT: @Viris hehe the people saw nothing.....
EDIT #2: Oh, you meant the paste bin...

 

[Viris]

Check before you speak(subcon and company)

 

[subcon959]

That's still directly linking to let people find the files and not allowed, I think you have to tell people to Google for the pastebin. But whatever maybe a moderator can take it from here.

 

[TheDuckMan64]

That's still directly linking to let people find the files and not allowed, I think you have to tell people to Google for the pastebin. But whatever maybe a moderator can take it from here.

Well then how about the mods go and take down the countless other threads that link to pastebins with illegal material?

 

[wurstpistole]

Still, it's absolutely redundant. The only problem people have is the wrong firmware files, despite every good tutorial telling exactly what the right files are and where to get them. Yeah, you pack some 12-05 rxtools nightly with the illegal firmware files that may be the correct ones, but it's still not allowed here. Then you add CtrBootManager, slap your "by Viris" advertisement in there, I mean what the hell. It's confusing and useless.

 

[TheDuckMan64]

Still, it's absolutely redundant. The only problem people have is the wrong firmware files, despite every good tutorial telling exactly what the right files are and where to get them. Yeah, you pack some 12-05 rxtools nightly with the illegal firmware files that may be the correct ones, but it's still not allowed here. Then you add CtrBootManager, slap your "by Viris" advertisement in there, I mean what the hell. It's confusing and useless.

Actually, no it's not. I get the "by Viris" bit, that's pointless as its others material that he threw together, but I did download the right firmware.bin, and rxtools still wouldn't work for me. Whatever different setting he has, it fixed my constant black screens.

 

[wurstpistole]

Actually, no it's not. I get the "by Viris" but, that's pointless as its others material that you threw together, but I did download the right firmware.bin, and rxtools still wouldn't work for me. Whatever different setting he has, it fixed my constant black screens.

He has no different setting. He has a firmware file that's generated by the python script every rxTools build comes with, a 12-05 build of rxTools which is the latest officially built nightly on lavanoid and CtrBootManager. That's basically the same people end up with when using my tutorial for rxTools.

 

[TheDuckMan64]

He has no different setting. He has a firmware file that's generated by the python script every rxTools build comes with, a 12-05 build of rxTools which is the latest officially built nightly on lavanoid and CtrBootManager. That's basically the same people end up with when using my tutorial for rxTools.

Didn't realise you'd made a tut too . What I meant by "different setting" was that he must have enabled something in the rxtools launcher that I didn't.

 

[wurstpistole]

Nope, he definitely did not. It's just a package of CtrBootManager (which is recommended anyway to increase boot rate), a relatively stable rxTools version and the right firmware file for O3DS. A combination some users for some reason are unable to put together themselves even when clearly laid out step by step in a tutorial. While the intention is noble, it's still not allowed to pack a firmware file into that, so yeah, back to square one.

 

[TheDuckMan64]

Nope, he definitely did not. It's just a package of CtrBootManager (which is recommended anyway to increase boot rate), a relatively stable rxTools version and the right firmware file for O3DS. A combination some users for some reason are unable to put together themselves even when clearly laid out step by step in a tutorial. While the intention is noble, it's still not allowed to pack a firmware file into that, so yeah, back to square one.

Idk what the hell I did wrong then, cause after checking my MD5's a bajillion times it still wouldn't work.