- Joined
- Dec 29, 2014
- Messages
- 2,758
- Trophies
- 1
- Location
- in a ziploc
- Website
- pbanjin.space
- XP
- 1,688
- Country
Did you read the wiki. There is a troubleshooting pageBlackScreen, not boot.
when I change the arm9loaderhax.bin V5.2 work :T
Did you read the wiki. There is a troubleshooting pageBlackScreen, not boot.
when I change the arm9loaderhax.bin V5.2 work :T
Updated to the latest Commit of Luma, now, when i start my console, it freezes @ the Boot Screen (not animated, just an custom boot screen)
Why's this?
N3DS-XL
Latest Git build (Latest commit 7e46046 an hour ago)
- Black screens and blue led on
- Can boot into Config Menu or any other payload fine
- Black screens and blue led on
- Can boot into Config Menu or any other payload fine
Was just going to post:Happened to me too, just go to the second newest commit or whatever. I tried on 3 different 3DSes, same issue all around, and I know for sure none of them were downgraded by Gateway stuff (otherwise I would not have been able to use commits before like some from 05/09).
Indeed: https://github.com/AuroraWright/Luma3DS/commit/d2f53626aece4e35ec09f29dbd7cd771ab218587now i have upgraded to a recent nightly build of luma3ds. The spalsh screen now stays on longer. i have the feeleing that this actually delays the boot times, is my hunch right?
Same situations here,is why i've reverted to stable one for nownow i have upgraded to a recent nightly build of luma3ds. The spalsh screen now stays on longer. i have the feeleing that this actually delays the boot times, is my hunch right?
Intresting point!yeah, i figured it might do that without delay, but i just deleted the splash screen, indeed it boots 3seconds faster. gonna live without boot splash, then.
yeah but i assumed it would take these 3 seconds from the time it was displaying a black screen anyways. but sincenit elongates the boot time i rather live without a splash.I made the splash last exactly 3 seconds.
Nope, to use NTR, you use the 9.6/10.2 firmware.bin file, which have svcbackdoor, etc... and compatible with NTR.Not a critical question, just informational: Currently running New3DS 10.7U sysNAND w/A9LH and Cakes v138 + NTR firmware.bin. Let's say I switched to the latest release of Luma3DS and then updated to 11.0. Would I lose access to BootNTR? Based on what I'm reading, even if you run A9LH + NTR firmware, you still lose access to svcBackdoor on ARM11, which means BootNTR won't work. Recent commits of Luma3DS fix this, but you have to compile it yourself.
Is this correct?
wrong and right. the latest commits do fix it. but you dont have to compile it yourself http://astronautlevel2.github.io/Luma3DS/Not a critical question, just informational: Currently running New3DS 10.7U sysNAND w/A9LH and Cakes v138 + NTR firmware.bin. Let's say I switched to the latest release of Luma3DS and then updated to 11.0. Would I lose access to BootNTR? Based on what I'm reading, even if you run A9LH + NTR firmware, you still lose access to svcBackdoor on ARM11, which means BootNTR won't work. Recent commits of Luma3DS fix this, but you have tocompile it yourself.(edit: I found that guy's page that compiles all the recent commits of Luma3DS)
Is this correct?