Closed 173210 closed 8 years ago
But a lot of work needs to be done on the docs before doing that. Nobody outside of DEVs can figure out what to do for n3ds firmware (and for all I know, n3ds support is completely screwed up at the moment). Removing the current binaries will cause drama before these two things are addressed.
Sent from my iPhone
On Oct 27, 2015, at 10:22, 173210 notifications@github.com wrote:
The common key Y got excluded from the current rxTools. I suggest to release a new version and remove all old binaries.
― Reply to this email directly or view it on GitHub.
@urherenow Actually updating docs is necessary. But the latest release doesn't include n3ds support, so I don't think n3ds support is necessary, although I'm working on fixing the issue now. :)
I opened #273. Why don't you make a new milestone for the next release and associate these issues?
@173210 3.0 release has to have n3ds support. So I'd say stop doing anything else, fix everything on n3ds (agb and twl patches, regionfree, data installation) and then, after 3.0 release, we can go back "experimenting" new features ;)
Is there anything to be done else solving #273 and #281?
@173210 Fix everything on n3ds (agb and twl patches, regionfree, data installation)
@AlbertoSONIC AGB and TWL patches can be features of 3.1. regionfree should be already OK. Issues related to data installation should be solved with pull request #280.
Region free has never been ok on N3DS. Everybody uses freemultipatcher for that.
Sent from my iPhone
On Nov 1, 2015, at 18:18, 173210 notifications@github.com wrote:
@AlbertoSONIC AGB and TWL patches can be features of 3.1. regionfree should be already OK. Issues related to data installation should be solved with pull request #280.
― Reply to this email directly or view it on GitHub.
@urherenow Isn't it solved with commit 116b0bf44ee10527fd121dab2d4d49870aaf99c8?
@173210 Nope rxTools 3.0 has to have same support on both o3ds and n3ds. If o3ds has twl patches, n3ds has to have it too
@AlbertoSONIC Why? The purpose of this suggestion is to release a new version excluding key Y as soon as possible.
Let's do this:
1)Delete all old builds (once the current one is stable) 2)Add a release to github, called rxTools 3.0 beta X
@AlbertoSONIC It's stable and doesn't need "beta". Well, or you may give another version (e.g. 2.7)
There are already some beta releases so we can (read: must) release another beta as this is not rxTools 3.0 final release. Also, rxTools is not stable, #273 and #281 are serious issues
I see. As I said, #280 solves #281. Please review (don't forget to test extended games both on old and new 3DS) and merge.
Unable to test right now. It's been so long since I upgraded on my N3DS, I decided to start from scratch. Now #279 is a problem for me. I get a top splash screen, black bottom, and I'm stuck right there... Just compiled myself with a fresh libctru...
Sent from my iPhone
On Nov 1, 2015, at 18:20, 173210 notifications@github.com wrote:
@urherenow Isn't it solved with commit 116b0bf?
― Reply to this email directly or view it on GitHub.
@173210 0 Tried to build from your fork, but can't. Anyway, I was able to boot directly into emunand using browserhax and ctrbootmanager (it boots directly with code.bin). So yes, the ninjhax files don't work because of the Cakebrah issue (I guess) and region free is definitely working. Works as well as other homebrew, anyway. It still does not allow DLC in other languages unless BootNTR is used with the language plugin. EDIT: What was it with extended RAM games and what needs to be tested? MH4 boots up just fine on N3DS, emunand 9.5 with latest rxtools. I'm assuming it is one of the extended RAM games...
But perhaps it's not using the same commit that the current rxtools uses. I do not have any trouble using ctrbootmanager, but launching via CN/Ninjhax 1.1b I get stuck with a black bottom screen.
It's working for me both ways now, since a new
Sent from my iPhone
On Nov 2, 2015, at 02:22, Steven Smith notifications@github.com wrote:
@urherenow It is using the same commit that current rxTools uses.
― Reply to this email directly or view it on GitHub.
@urherenow Just in case. If you can please check.
Before removing old versions : On old 3DS, rxTools <= 2.6 which used GW's Launcher.dat template work on browser that does not match the FW version (cartridge-updated). CakeHax provides SPIDER exploit as well but it lacks supports for cartridge-updated devices.
I fail to see the point. Browserhax can be used initially and a new browser can be installed via ctrbootmanager->HBL->FBI. Or am I mistaken?
Browserhax only run on >= 9.0 Users who wants to update their 3ds to 9.x using rxTools have to use rxTools 2.5.2 w/ devmode if theirs was updated via cartridge. Or one can tell them to downgrade 3ds using GW launcher and to use MSET-PASTA to update their 3ds but that is overcomplicated.
The point : 4.x-8.x old 3ds which was updated via cartridge cannot run current rxTools via browser. And to update those, rxTools 2.5.2 have to be used. Or, we can make a "legacy" version which uses GW Launcher.dat template. (Of course that will be of no use for N3DS)
Not according to https://github.com/yellows8/3ds_browserhax_common (you must be thinking of menuhax), and the current rxtools build has working pasta mode. Regardless, one can update to 9 with super smash brothers, and use one of several methods to get their browser updated. You don't need pasta/devmode or anything other than a way to run a cia manager, and you don't need any version of rxtools at all. ctrbootmanager can launch HBL with the permissions that FBI needs, as can minipasta and a bunch of other stuff. And at 9... the old launcher.dat method to launch rxtools isn't needed by anybody anyway.
Granted, it's personal preference, but I think there is no reason for anybody to remain below 9.2 anymore. There are plenty of ways to get there, including getting the browser updated, with or without rxtools. < 9.x just isn't needed anymore and if someone wants to stay there, then it's their own choice and they'll have to deal with it.
@urherenow :+1:
@urherenow You have misunderstading. That github readme says supported BROWSER version, not FW version. So you can run browserhax on FW 9.0 with older browser, but not on system version < 9.0 with any browser due to lack of payloads. And for japanese console, 9.0-9.2 update is not available via cartridge.
And I am saying about the consoles that cannot run HBL and the latest rxTools like 4.x-8.x ones with older browser. (They cannot access ALL CAKEHAX BASED HACKS) They can not run HBL, rxTools 3.0 and of course ctrbootmanager to boot minipasta or FBI. TO UPDATE THEIR CONSOLES to 9.0+ or update their browser, older rxTools is the best way.
@kot2002
TO UPDATE THEIR CONSOLES to 9.0+ or update their browser, older rxTools is the best way.
Why?
Okay I'm not sure what's going on here, but I had a 100% stock OoT 3DS that originally came with 4.x and was updated over the Internet to 9.2 and its accompanying web browser, and I hacked it using BrowserHax, and originally loaded rxTools using it. On Mon, Nov 16, 2015 at 6:47 PM 173210 notifications@github.com wrote:
@kot2002 https://github.com/kot2002
TO UPDATE THEIR CONSOLES to 9.0+ or update their browser, older rxTools is the best way.
Why?
— Reply to this email directly or view it on GitHub https://github.com/roxas75/rxTools/issues/272#issuecomment-157211413.
@173210 Those 4.x-8.x consoles with older browsers cannot run anything except for GW launcher.dat based ones.
So they have 3 options to update to 9.0-9.2:
@b- What we are talking about is not internet-updated ones, but cart-updated.
Oh, I understand now. Sorry! On Mon, Nov 16, 2015 at 7:02 PM Dean notifications@github.com wrote:
@b- https://github.com/b- What we are talking about is not internet-updates ones, but cart-updated.
— Reply to this email directly or view it on GitHub https://github.com/roxas75/rxTools/issues/272#issuecomment-157213783.
@kot2002, no, that's just your opinion, not a necessity. Pasta is still out there and will not go away when killing the old rxtools versions.
@urherenow So now they have to buy cubic ninja?
Nevermind... I guess Pasta needs CN.
@kot2002 Sorry, but I don't know how to update with rxTools.
Anyone not on 9.x or above most likely has any number of hax in use already, and you will never find something lower on the shelf anymore buying new ones. < 9.0 needs to die.
@kot2002 also... since you mention downgrading with Gateway, what about using reinand via mset? Will that run on 4.x?
Or PBT or whatever
Now you are saying those who own older need to die?
PBT.. that is the same as option 1. They need DS cartridge to run it.
And... I think it is you that is misunderstanding. I read nowhere that says browserhax requires 9.0 or above. It does not. That is only menuhax/themehax.
go to 3dbrew..
And no... <9.x support needs to die (not the people). Most people who are below 9 have upgraded via browser before, or otherwise have a Gateway or some other working CFW installed. I don't see any newcomers appearing with this issue that you seem to be so worried about.
*via network
I'm at work so I'll stop after this, but if all else fails... This is the Internet. Even after killing old versions, they will still pop up in Dropbox and mega and such, if anybody truly needs and/or wants to find it.
That is not true. There are still a plenty of <9.0 old 3ds's in stock. And you can easily find people who stuck with weird version like 7.0.0-4. Abandoning compatibility is the worst thing ever.
And I just checked 3dbrew. Take your own advice and read it. browserhax DOES work on lower firmwares; just not to launch .3dsx format stuff. It can launch a code.bin or whatever (not that I can think of anything made to work with it, but still...) Look at the section below the secondary exploits section.
Here is a device which works with 4.5. I'll try to use browserhax...
@urherenow You are wrong. Lacking of payload means you cannot do anything.
The common key Y got excluded from the current rxTools. I suggest to release a new version and remove all old binaries.