Oh wow, wait what do I even do just copy it and name it a_bl.bin? That wasn't clear, no wonder I had problems beforehand.. Thanks daxtsu
Oh wow, wait what do I even do just copy it and name it a_bl.bin? That wasn't clear, no wonder I had problems beforehand.. Thanks daxtsu
No, a_bl has no extension. a.bin is decrypt9, and a_bl is a blank file/garbage file. It doesn't matter what goes in it, as arm9select only looks to see if a_bl exists in the folder. If it does, it turns the lights on. If it doesn't, no lights.
Sorry, I wasn't clear I literally meant having decrypt9 named to a.bin and then copy it and name the copy as a_bl.bin to set off the flag. Still no lights though...
EDIT: Yeah I understand now, thanks no extension. Having a noob moment here
Last edited by mungry,
Hmm I have it all set up correctly. It launches default.bin (ARN) and pressing up/down on the d-pad launches the respective files with backlight.
However I still get that initial screen flash when booting up (cold as well). I've updated to 1.1. but I'm still getting it.
However I still get that initial screen flash when booting up (cold as well). I've updated to 1.1. but I'm still getting it.
Oh right that would make sense. Unfortunately it would seem I have to manually compile it myself? I'm new to github so unless there's a release I'm a little lost.
does arm9select work for anybody using delebile arm9loaderhax with screen init? @Aurora Wright updated the loader of AuReiNand to function similar to this but it will not work if you are using the @FIX94 arm9loaderhax fork (like me) due to @FIX94 setting backlight to 0 in his fork of arm9loaderhax. If AuReiNand could set backlight to 0 like @FIX94 does and use the _bl files to determine which payloads load with backlight it would be integrated in a way that regardless of which arm9loaderhax fork you have installed (delebile(backlight set to 0x39), Fix94(backlight set to 0x0) it would be awesome cause no one would have to change arm9loaderhax install to get maximum use. Maybe I represent the small percentage of people with @FIX94 arm9loaderhax fork installed, but I do no use a splash.bin for AuReiNand so leaving the backlight off allows the 3DS to boot without the splash.bin backlight flash that was annoying to @FIX94. Feel free to chime in if you think I'm crazy. Also it seems like AuReiNand requires alot of different button combos to load it's many possible payloads where arm9select requires only 1 button to be held. The implementation that @Aurora Wright has added to AuReiNand is a step in the right direction, however it seems as far as ease of operation arm9select requires less input from user to achieve the same result with or without backlight set in arm9loaderhax.
Edit: Sorry for the novel but I should add if you still want splash screens for AuReiNand all you have to do is add the default_bl to the arm9select folder (AuReiNand is my default yours may be select, start, a or b so in this case obviously you would need enteryourkeyhere_bl to achieve this)
Edit: Sorry for the novel but I should add if you still want splash screens for AuReiNand all you have to do is add the default_bl to the arm9select folder (AuReiNand is my default yours may be select, start, a or b so in this case obviously you would need enteryourkeyhere_bl to achieve this)
Last edited by stl25,
It's not my duty to support a non-standard A9LH environment (Fix94 made it for his app specifically). If you don't want the splash screen and want to use my arm9select-like loader, just switch to a non-screen-init A9LH. If it's needed, I can upload mine on github, or you can just get an older version of delebile's github repo.
Also, I can't see what these "crazy button combos" are, but let's not derail the thread.
Last edited by Aurora Wright,
D
Deleted User
Guest
If you're using Deb screen init fork, A9Select works fine. You don't need the _BL files since the screen is initialized already (was how I was running before)
I don't think there's any crazy button combos. Maybe he's referring to Holding L+R+Boot Key of choice. (only limitation being you can't use L, R, or A)
Only solution if you wish to use AuRei boot manager is grab an older copy of A9LH without the screen init if you don't want the backlight on since AuRei turns it on for each payload.
I don't think there's any crazy button combos. Maybe he's referring to Holding L+R+Boot Key of choice. (only limitation being you can't use L, R, or A)
Only solution if you wish to use AuRei boot manager is grab an older copy of A9LH without the screen init if you don't want the backlight on since AuRei turns it on for each payload.
@Aurora Wright, I was just trying to find out if arm9select works with screen init the same way it does without screen init. If is does it seems rather than have people changing arm9select forks (I jumped on @FIX94 arm9loaderhax pretty early as I choose not to use the splash and disabling the backlight looks more pleasing that screen comes on screen turns off screen turns back on to load AuReiNand. I was commenting on his unique and simple approach to this issue by using the _bl files to only enable backlight when required or desired being the key word. Is this style of implementation he chose possible in your loader.bin for AuReiNand. I appreciate your CFW I am just trying to prevent having to switch arm9loaderhax for the 3rd or maybe 4th time. I currently use 3.9 AuReiNand but opted to stay on arm9select only due to not wanting to change arm9loadhax install nothing more. Sorry if I came across as whining or complaining. That is truly not my intent.
--------------------- MERGED ---------------------------
@gunner007 , thanks for your reply. I just thought it was kind of cool how @FIX94 used the _bl files to determine when backlight is desired and rather than change arm9loaderhax install again, maybe @FIX94 backlight method could be used in AuReiNand's loader to cover all arm9loader forks (some with or without screen init). Seems like this implementation would allow you to remain on whatever fork of arm9loaderhax you currently have installed. Again thanks for your reply.
--------------------- MERGED ---------------------------
@gunner007 , thanks for your reply. I just thought it was kind of cool how @FIX94 used the _bl files to determine when backlight is desired and rather than change arm9loaderhax install again, maybe @FIX94 backlight method could be used in AuReiNand's loader to cover all arm9loader forks (some with or without screen init). Seems like this implementation would allow you to remain on whatever fork of arm9loaderhax you currently have installed. Again thanks for your reply.
D
Deleted User
Guest
I can't see doing that. There's just so many forks and versions. (TBH poor Aurora already has so many flags 
)
TBH though, they're all open source. You can just change the code as you see fit.
That's basically all I did. Edited all the CFW/A9LH/A9Select to run out of a single folder. (I goofily even add a version string into my splash screen so I can actually keep up with what I'm doing)
Though I'm a bit lost on why you would need that with Aurora's build.
At the point you're booting into his loader, any additional payload you launch would need screen init anyways (d9, uncart, emunand9)
)TBH though, they're all open source. You can just change the code as you see fit.
That's basically all I did. Edited all the CFW/A9LH/A9Select to run out of a single folder. (I goofily even add a version string into my splash screen so I can actually keep up with what I'm doing)
Though I'm a bit lost on why you would need that with Aurora's build.
At the point you're booting into his loader, any additional payload you launch would need screen init anyways (d9, uncart, emunand9)
Last edited by ,
@gunner007, that is what I have done. To keep @Aurora Wright folder structure for AuReiNand I compiled arm9select to look for the payloads in /rei/payloads. This way I can use arm9select like @Aurora Wright loader rather than change my arm9loaderhax. @Aurora Wright my apologies if I came across as demanding, I appreciate every release from you and not to brown nose but I am currently only using AuReiNand cause I really like the sysNAND access and the implementation of the second emunand may allow me to play around with Cakes or future CFW on a separtate emunand. I see how my inquiry may have upset you and I am sorry. I was only trying to be constructive in your loader. Thank you for your great work.
Yeah i'd rather use a separate boot loader rather than one implemented into a CFW. The bootloader has priority over everything, allowing you to launch things such as Decrypt9 before you even boot into a CFW, which I like the idea of way more.
AuReiNand is using the concept of arm9select in it's loader as per the changelog. The current advantage of using arm9select is currently it is set up to handle all version of arm9loaderhax and requires only 1 button to be pressed to load the payload vice press the matching button together with L and R to load the payload (as per AuReiNand changlelog).
Function wise they are identical as they are both loading the payload at power on, just less user input is currently required to do this in arm9select.
Last edited by stl25,
in the end it comes all down to personal preference, probably a lot of developers have their own code of it and you can just be happy to see people like me and aurora wright have no issue with also giving out source code for everyone to try out and play around with without having to write their own program, they are plenty of people who have some great stuff but dont share it.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Veho:
Illinois is working to ban toxic food additives that have been banned for decades in other countries; additives that can be replaced and all those countries still have Skittles and Mountain Dew. Title of the piece: GUBMINT WANTS TO TAKE AWAY YOUR CANDY -
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer". -
-
-
-
-
