Homebrew R4 Stage2 TWL Flashcart Launcher(and perhaps other cards soon™)....

[Link_of_Hyrule]

unknown cart? Sounds like a hardware problem. Perhaps bricked/dead cart? It's supposed to have a unique id followed by "TWL". Even original R4 has a valid id in devmenu. Unknown Cart means it failed to init correctly and could not read the rom header.

I'm having the same issue mine says unknown card it worked previously with the patch TWL but so isn't working without the patch TWL and AuReiNand.

EDIT: I was able to get it to come up as 4153d41 TWL Card in the dev menu but so far still no boot. It shows up as the blank card in the normal slot but both the Wood r4 launcher and the regular card go to the black screen with text when I try to use them. It worked previously and the card works on my DS Lite. I fixed this little spring in the microSD Card slot so hopefully it works better now.

EDIT2: I'm apparently retarded and missed this step on the AuReiNand OP "To enable AGB_FIRM and TWL_FIRM patching, just also copy the firmware_agb.bin and firmware_twl.bin files for your console from the FIRMs.7z." It works now.

 

[Dr Orochi _Autism PH.D.]

So, I'm on rxtools 3.0 beta 2, and I'm trying to use my original r4 with this, wood r4 launcher and the r4 evolution for ds launcher, and neither are working. Each look like they try to boot the card, but then say that an error has occurred and the power needs to be turned off in Sysnand and Emunand

 

[Apache Thunder]

Don't use rxTools 3.0 Beta 2. It's TWL patches are outdated. I'd recommend switching to Aureinand. It now has TWL patches.

 

[Deleted User]

Don't use rxTools 3.0 Beta 2. It's TWL patches are outdated. I'd recommend switching to Aureinand. It now has TWL patches.

I tried DSTT one, and R4 one, but my linker doesn't start.

I want to use my old R4 (this one) (notice the "NDSL/NDS" mark, not "DSi" or whatever); but it doesn't work.

I have these files on my R4 SD Card.

 

[Dr Orochi _Autism PH.D.]

I tried to use the wood launcher, and the menu popped up, but no games or anything showed up. Even selecting the microsd and folder icons does nothing. Along with the r4 launcher actually booting, and then just showing a "Loading..." screen

 

[Apache Thunder]

What console are you using? If it's a n3DS or 2DS, you may have contact issues. Most original R4s are using cheap PCB designs and the contact pins are a bit too short. It seems the design of the slot of the n3DS and 2DS are a bit different then the original 3DS. Of coarse the R4 came out when the DS/DS Lite was still a thing. So it's not too surprising to see issues crop up on consoles that came out nearly a decade after the R4 was first introduced.

Push in the cartridge past the click and hold it there. Then try WoodR4 again. if it works then, it's a contact issue with the slot. The most you can do about that is insert a slip of paper in between the cartridge and the slot to help keep it from popping out too far.

 

[Dr Orochi _Autism PH.D.]

So, woodr4 is launching, but everything is blank, and nothing is showing. I put a Digimon Dusk rom on the root of the sd, formatted to fat16, and in a folder labeled "Games". i'm using wood v 1.62, do i need subfolders with the games, or do i need to install or put something else on my sd? I switched to aureinand as well (o3dsxl)

 

[AtlasFontaine]

So, woodr4 is launching, but everything is blank, and nothing is showing. I put a Digimon Dusk rom on the root of the sd, formatted to fat16, and in a folder labeled "Games". i'm using wood v 1.62, do i need subfolders with the games, or do i need to install or put something else on my sd? I switched to aureinand as well.

If it doesn't show anything besides the menu and a white screen, then it means that it isn't detecting your r4 (or it is incompatible). Try ejecting the r4 and opening the launcher without it and you'll see that it does the same.

 

[Dr Orochi _Autism PH.D.]

If it doesn't show anything besides the menu and a white screen, then it means that it isn't detecting your r4 (or it is incompatible). Try ejecting the r4 and opening the launcher without it and you'll see that it does the same.

Oh yeah, I removed the cart and it shows nothing, I tore the sticker off a while ago, so I think my cart is an r4v2 or some clone of it

 

[AtlasFontaine]

Oh yeah, I removed the cart and it shows nothing, I tore the sticker off a while ago, so I think my cart is an r4v2 or some clone of it

Well, it seems like this launcher doesn't work with original R4 clones.

 

[arabtm]

Has anyone tried to get this to work with the M3 DS Simply?


EDIT: NVM got it to work. New question is there a way to for the top screen to stretch? Also is there a hot key in R4 wood to exit out of DS games back to the DS Game selection menu?

Hi. Could you kindly explain how did you manage to make M3 DS Simply to work? You're using 3DS I hope?
thanks.

I bought an R4 clone last week, and when I somehow bricked the cart, by messing arround with it's kernel. So, I hope I can reuse my M3DS simply, but not sure which firmware I should use now. I want to avoid any bricking again

 

[Link_of_Hyrule]

Hi. Could you kindly explain how did you manage to make M3 DS Simply to work? You're using 3DS I hope?
thanks.

So I'm pretty sure I got the wood r4 http://www.r4wood.com/pages/wood-r4-kernel.html from here which goes on the actual M3 Simply (you should backup your old stuff however). After that install the wood R4 cia from the OP of this thread be sure to install it on both the sysnand and emunand. Make sure if you're using AuReiNAND to uninstall the patched AGB and TWL CIA firms and install the originals back in and follow this step from the AuReiNand thread "To enable AGB_FIRM and TWL_FIRM patching, just also copy the firmware_agb.bin and firmware_twl.bin files for your console from the FIRMs.7z." My card was kind of finicky so I had to actually unscrew it and screw it back together and stick it in my DS Lite to test it and such but I think that's really all I did to get it working.

 

[arabtm]

So I'm pretty sure I got the wood r4 http://www.r4wood.com/pages/wood-r4-kernel.html from here which goes on the actual M3 Simply (you should backup your old stuff however). After that install the wood R4 cia from the OP of this thread be sure to install it on both the sysnand and emunand. Make sure if you're using AuReiNAND to uninstall the patched AGB and TWL CIA firms and install the originals back in and follow this step from the AuReiNand thread "To enable AGB_FIRM and TWL_FIRM patching, just also copy the firmware_agb.bin and firmware_twl.bin files for your console from the FIRMs.7z." My card was kind of finicky so I had to actually unscrew it and screw it back together and stick it in my DS Lite to test it and such but I think that's really all I did to get it working.

thanks for the swift reply! I'll try to use wood kernel as you advised.
I'm using A9LH Sysnand Cakes CFW N3DSXLUS, so I guess it measn I need to patch the TWL_FIRM too?
I've been thinking of changing to ARN CFW due to this patching

 

[Link_of_Hyrule]

thanks for the swift reply! I'll try to use wood kernel as you advised.
I'm using A9LH Sysnand Cakes CFW N3DSXLUS, so I guess it measn I need to patch the TWL_FIRM too?
I've been thinking of changing to ARN CFW due to this patching

IDK what advantages cakes has but the thing I like about AuReiNAND is that (with a few exceptions) after the first install updating to the new version is literally replacing one file and that's it.

 

[arabtm]

IDK what advantages cakes has but the thing I like about AuReiNAND is that (with a few exceptions) after the first install updating to the new version is literally replacing one file and that's it.

I see. well, I'm using Cakes just because I was following the A9LH tutorial at that time, but these CFWs are progressing so fast now
I'll check how to move to ARN from Cakes.

 

[Link_of_Hyrule]

I see. well, I'm using Cakes just because I was following the A9LH tutorial at that time, but these CFWs are progressing so fast now
I'll check how to move to ARN from Cakes.

Literally all you do is copy the arm9loaderhax.bin to the root of your sd card from the AuReiNAND release zip with the aurei folder if you have any a9lh payloads put them in the payloads folder labeled the button you want to use to launch them at boot. Copy the proper firms from the firms.7z file and I'm pretty sure that's it. When you want to update just update the arm9loaderhax.bin file you don't need to do anything with any of the other files unless the firms get updated in which case I'm sure they'll post and say we need to update those.

 

[arabtm]

Literally all you do is copy the arm9loaderhax.bin to the root of your sd card from the AuReiNAND release zip with the aurei folder if you have any a9lh payloads put them in the payloads folder labeled the button you want to use to launch them at boot. Copy the proper firms from the firms.7z file and I'm pretty sure that's it. When you want to update just update the arm9loaderhax.bin file you don't need to do anything with any of the other files unless the firms get updated in which case I'm sure they'll post and say we need to update those.

I see. I do have one concern though. I updated my A9LH with arm9select, so I'm not using CTRBootmanager anymore. I heard arm9select doesn't work properly with ARN, since ARN also have it's own screen_init mechanism? or am I just talking rubbish?
I'm just a bit worried modifying again my A9LH could cause any bricking.

 

[Link_of_Hyrule]

I see. I do have one concern though. I updated my A9LH with arm9select, so I'm not using CTRBootmanager anymore. I heard arm9select doesn't work properly with ARN, since ARN also have it's own screen_init mechanism? or am I just talking rubbish?
I'm just a bit worried modifying again my A9LH could cause any bricking.

with AuReiNAND you don't need any kind of payload selector because it has it built in with the payloads. Is there a thread I can look at the arm9select at?

 

[arabtm]

with AuReiNAND you don't need any kind of payload selector because it has it built in with the payloads. Is there a thread I can look at the arm9select at?

I used from here:
https://gbatemp.net/threads/arm9select-my-own-take-on-a-a9lh-file-select.417803/page-7

here's the quote from Apache Thunder on the same page, that makes me hesitant to change to ARN for now. I don't know yet how to deal with this.

@FIX94:

"Doing screen init but leaving backlight at 0x0 is a non-standard environment. The proper way for Fix94 would be to NOT do screen init in stage2 and doing it fully from inside Arm9Select. This way detection wouldn't be borked. This is not an issue with Aurei itself."

This is a quote from Aurora. Your version of A9L is causing issues with Aureinand now. (hangs if booted without config file). Perhaps moving screen init into Arm9Select would be better?

 

[Link_of_Hyrule]

I used from here:
https://gbatemp.net/threads/arm9select-my-own-take-on-a-a9lh-file-select.417803/page-7

here's the quote from Apache Thunder on the same page, that makes me hesitant to change to ARN for now. I don't know yet how to deal with this.

I don't see the actual download for the arm9select. Is it just a .bin file that you put in the root of your SD Card and make a folder for it with other payloads?