- Joined
- May 2, 2016
- Messages
- 449
- Trophies
- 0
- Location
- the deepest depths of hell.
- Website
- crimson.ninja
- XP
- 1,510
- Country
Install the New Homebrew Launcher CIA. It's on FBI under TitleDB. Open that CIA, and the HBL will load.and how to do that ?
Install the New Homebrew Launcher CIA. It's on FBI under TitleDB. Open that CIA, and the HBL will load.and how to do that ?
Give me reproducable steps and open a GitHub issue. I need more than just "Still crashes".still crach
Rop code is running. But idk what's happening. Try removing the rop code from the SD and rerun the exploit.ok.
i open hombrew loader the top screen shows "the homebrew ropbin is ready"
the botton screen is yellow .
the system stop (crash) force to reboot
There's a difference ?
--------------------- MERGED ---------------------------
Ok , i'll wait
There's a difference ?
--------------------- MERGED ---------------------------
Ok , i'll wait
Well, yes. ReiNAND has had firm partition protection for a while now. So, updating will not overwrite your firms with a retail NF. However, it still relies on external firmware files. So, if Nintendo updates NATIVE_FIRM, the "native_firmware.bin" file may need to be updated before the new FW version can be booted by Rei-Six. As history has shown, this depends on if Nintendo updates the minor version, and whether they make the other apps like the home menu require this as the new minimum version required in order to run. That is why rxTools remained usable for so long without updates (until 11.2 came out IIRC). The home menu remained bootable with 9.6 for all that time. But Nintendo probably won't make that mistake again.
Luma has been able to avoid this problem because it has the ability to extract the firmware files straight from the CTRNAND partition. But that also requires it to reload itself with it's reboot patches. Until recently, this required a "path.txt" file unless you were using Luma as the main payload (which I never have). I'm sure Crimson would love to add this feature, but it's complicated, and it was far more important to add these other patches first.
It's not really that hard to extract a new NF though. I could easily create a GM9 script that extracts the current NF (actually, I already have that part written for me, thanks to d0k3), copies it to the "rei" folder, and decrypts it, assuming that would work. I have to admit, I'm not really sure how the current "native_firmware.bin" is generated. Though I'm guessing they're just using "copy/b" or "cat" to concatenate them together, and that the CFW sorts them out via a byte pattern search for the header or something.
You can update to 11.6 and Rei-Six.So...
At the moment i can't update the system with Rei6 , because rei6 doesn't support it
Rei-six + GM9 Bootloader + NTR > LumaIt is. (Just saying, looking at the change log would have answered this question.) They were giving instructions to get gm9 as a bootloader + Rei-six which is my recommended setup.
Not at the moment. I use b9s' screeninit which uses the 3rd brightness setting (in terms of Luma Brightness.) I can look into adding GM9s screeninit though.
Funnily enough, that's my current setup. ( ͡° ͜ʖ ͡°)Rei-six + GM9 Bootloader + NTR > Luma
Nope. And that should be placebo, the splash screen is longer, that's about it.does the size of my microSD card affect the boot time? I notice the latest release from 3 days ago boots a lot slower than the previous one
ohhh ok thanks..Nope. And that should be placebo, the splash screen is longer, that's about it.