Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by Aurora Wright, Jan 19, 2016.
Because it's time to upgrade!
I heard Hamcha wasn't updating the application anymore. I'm not very good with coding. @KunoichiZ
You're asking the wrong person. I wouldn't know the first thing about updating the application for sighax support, unless it's as simple as changing where the updater gets its files from.
Just make it download the .firm instead.
I'll try my hardest, but I'm not sure what all I would have to change to make it work properly. Why is Hamcha's Luma Updater still linked in Plailect's guide though?
Perhaps you should send Plailect the link to your Luma Updater.
Just realized that also Decript9 is borked till it gets a .firm version. Yeah no worth a dime to update a9lh to strapon9 just yet.
I will once I figure out how to make it work properly. And I'll need someone with sighax installed to test it as I don't want to upgrade right this moment.
Actually, StarUpdater-UN supports it.
Learn something new everyday.
Would having Luma's boot.firm on a a9lh system mess up anything? I can test to see if it at least downloads the .firm correctly.
No, but it won't run.
I figured that. Thanks! I'll keep you guys updated on my progress.
I can test it. Just send me the version that downloads the .firm payload as soon as you finish it. Of course I need to install SigHax first... Let me get right on that.
I can confirm that boot.firm from the latest version Luma3DS downloads correctly! Now whether or not it works on a system with sighax, that needs to be tested.
SigHax shouldn't affect it.
What I meant was if it would download the newest boot.firm when it comes time for Luma to update. If people update to sighax right this moment, then there's no need for Luma Updater.
I mean, if it just replaces files on the SD card, I don't see why it wouldn't work.
I do see your point now. For contacting Plailect to send him my version of Luma Updater, would I just make an issue on the guide's Github page?
it's better since users can dump their own bootrom and otp at any point, which means they can do things like de/encrypt games on PC without a 3DS in the middle.
dropping older entrypoints is less code to maintain, and I think devs really don't want to support a9lh anymore when b9s is easier and better to work with.
as for Decrypt9WIP, the newer tool is GodMode9 (which got b9s support too) and I don't know if D9WIP will be updated.