I don't know if it functions at all on Old3DS; I haven't tested it. I know 3.3 worksit work with luma thanks but its safe to use 3.4 preview on o3ds?
I don't know if it functions at all on Old3DS; I haven't tested it. I know 3.3 worksit work with luma thanks but its safe to use 3.4 preview on o3ds?
It work's fine on o3dsI don't know if it functions at all on Old3DS; I haven't tested it. I know 3.3 works
What does the topic of this thread say?To use this do I need a firmware.bin in the luma folder?
Again...? Just help...I said multiple times that even after deleting the firmware.bin I keep getting firmware not supported :/What does the topic of this thread say?
Topic reading is essential to your previous questionAgain...? Just help...I said multiple times that even after deleting the firmware.bin I keep getting firmware not supported :/
FYI I read the topic and was mostly about 3D Banner for BootNTR with 11.0 NATIVE_FIRM. While reading I saw this sentence quoted above, and I thought I could use the "new" BootNTR myself, but seems not working for me... And now I am just asking why. If you do not wanna help just say "no" "this is not the right place to ask" simple as thatIt means it works on the 11.0 firmware. No need to use the the old 10.2 firmware any more. If using Luma you can delete the firmware.bin file from the luma directory so it starts using the updated firmware.
- What system?FYI I read the topic and was mostly about 3D Banner for BootNTR with 11.0 NATIVE_FIRM. While reading I saw this sentence quoted above, and I thought I could use the "new" BootNTR myself, but seems not working for me... And now I am just asking why. If you do not wanna help just say "no" "this is not the right place to ask" simple as that
- N3DS- What system?
- What CFW do you use?
- Emunand? yes or no
- What firmware version is your Emunand
- A9LH system? yes or no
And yes i'm to lazy to check your previous posts to check that out.
I had to delete the config.bin of Luma then it worked. Thanks for the help really appreciated it.I would start with removing anything bootntr related with FBI
Remove anything bootntr related from your sd
Check if you have latest Luma3DS to be sure for the svcbackdoor fix
Then reinstall the autoexit version and ntr.bin to your root of the SD
If it still doesn't work, try with the older ntr.bin (3.3 i think) (i have no link for that)
If it still doesn't work, i would check if you are using a frankenfirmware on your system before attempting anything else (there are other threads for that.
Yes I deleted config.bin and firmware.bin from luma folder, than I boot the into Luma Configuration, set it up again and installed BootNTR with autoexit and worked perfectly except that sometimes after exiting it auto launch whatever is highlighted with the cursor at the time of exit, but that happened to me twice only@Ramzh so you deleted config and firmware from the luma folder then installed bootntr 11-0 native firm with FBI and it worked?
HAHAH my problem was i named the plugin folder "plugins"... i took the "s" and it worked rofl...
@azoreseuropa is a cheat engine if u want to call it that way..
I think that is trueCan someone tell me what version number their on when enabling the options screen Y+X. I have 3.4 Preview 2 on my N3DS a9lh 11.0 fw but just want to confirm this. I guess this is based on the version "bin" no? So if you use the ntr.bin from 3.2, it would show that in the options.
3.4 is good, even 3.3 works fineCan someone tell me what version number their on when enabling the options screen Y+X. I have 3.4 Preview 2 on my N3DS a9lh 11.0 fw but just want to confirm this. I guess this is based on the version "bin" no? So if you use the ntr.bin from 3.2, it would show that in the options.