BootNTR has worked on 11.0 for along time now it was not just updated in fact I made a thread with Auto-exit and Non-Auto exit versions with 3D bannerAFAIK if you use the latest version of BootNTR (the one that was just updated) and use 11.0 firmware.bin it SHOULD work. But I haven't bothered to test it myself (have to find where to get 11.0 firmware.bin) nor do I care to read through all 73 pages to try to find the answer.
AFAIK if you use the latest version of BootNTR (the one that was just updated) and use 11.0 firmware.bin it SHOULD work. But I haven't bothered to test it myself (have to find where to get 11.0 firmware.bin) nor do I care to read through all 73 pages to try to find the answer.
Hence why you would need 11.0 firmware.bin. If you have that and a CFW that can use it it should in theory work right now@TheCyberQuake That"s still need to fix since it was fixed to work with 11.1.0-X Home Menu but 11.1.0-X NATIVE_FIRM isn"t fixed yet.
Hbl payload has been updated for 11.1What is not totally clear for me:
I have al9h with Luma3DS.
That has firmware update protection.
But earlier in the thread someone said that my CFW will work, but homebrew will not.
Will my HBLauncher (which I have installed as a CIA) not work anymore? And what about other homebrew installed as CIA? Can I still install other homebrew as CIA?
No iirc a build was released today that supports the new homemenu, and with an 11.0 firmware.bin you would have 11.0 nativefirm running which would then fix NTR temporarily.Which version of BootNTR was just updated? You mean the one updated in June that used to be in Plailect's guide?
No iirc a build was released today that supports the new homemenu, and with an 11.0 firmware.bin you would have 11.0 nativefirm running which would then fix NTR temporarily.
Yes, I know. Hence why I said that using a 11.0 firmware.bin would probably be a temporary fix for 11.1 users because it already supports the 11.1 homemenu.@TheCyberQuake Because BootNTR was updated before to support 11.0.0-X NATIVE_FIRM.
Alright, cheers.@TheCyberQuake Because BootNTR was updated before to support 11.0.0-X NATIVE_FIRM.
--------------------- MERGED ---------------------------
@Wabsta It works, only you need to put the new payload manually in the SD Card or it the Launcher will downlaod it when you start it if you are connected to Internet.
AFAIK if you use the latest version of BootNTR (the one that was just updated) and use 11.0 firmware.bin it SHOULD work. But I haven't bothered to test it myself (have to find where to get 11.0 firmware.bin) nor do I care to read through all 73 pages to try to find the answer.
Which option would that be in d9?You can dump native firm 11.0 with D9 and then rename it to firmware.bin
Which option would that be in d9?
Sent from my SM-G386T using Tapatalk
Which option would that be in d9?
Sent from my SM-G386T using Tapatalk
I forgot Luma removed the ability to use firmware.bin on anything 6.x and greater (which imo should not have been done). So I'll have to change back to corbenik tomorrow to test ntr with 11.0 FIRM on 11.1
Sent from my SM-G386T using Tapatalk
"Luma3DS updater" only updates luma, the "custom firmware". use system settings to update the system to 11.1.0-34I did all parts of plailects guide, when 11.0 was the latest version.
Is it safe for me to use luma3ds updater to update to 11.1?
I want to update that firmware, which normally boots at startup. It is shown as 11.0 in the System settings.
(After full Plailects Guide, this should be the custom firmware on SysNAND, right?)