In the source. Stop being an idiot, please.Where does it state otherwise?
In the source. Stop being an idiot, please.Where does it state otherwise?
Ok ok, I'll do that. Thanks for helping @Filo97 as well.In the source. Stop being an idiot, please.
Holding L, R or L+R boots me into emunand.It needs to be in the rei folder...
And what you quoted from the OP is for the updated sysnand flag...
You need to hold it while pressing power, until you see your sysNAND. Make sure the firmware90.bin is in the rei folder.Ok ok, I'll do that. Thanks for helping @Filo97 as well.
--------------------- MERGED ---------------------------
Holding L, R or L+R boots me into emunand.
Since I use BootCtr9, I hold it when the splashscreen comes up. Also, it states in the description that holding L or R will boot you into an emunand.You need to hold it while pressing power, until you see your sysNAND. Make sure the firmware90.bin is in the rei folder.
Ok, I held it when the power turned on, and booted into sysnand. I got the "An error has occured" screen, and tried again. Now when I try it, it still boots me into emunand.Since I use BootCtr9, I hold it when the splashscreen comes up. Also, it states in the description that holding L or R will boot you into an emunand.
?
I think that you have to hold it before. (And I would recommend you to use CtrBootManager9 instead.)Since I use BootCtr9, I hold it when the splashscreen comes up. Also, it states in the description that holding L or R will boot you into an emunand.
?
Are you sure that you're using the correct firmware90.bin ? And is your sysNAND functional, at least?Ok, I held it when the power turned on, and booted into sysnand. I got the "An error has occured" screen, and tried again. Now when I try it, it still boots me into emunand.
Yes, I'm using the right firmware90.bin and yes my sysnand is functional. Holding nothing boots me into sysnand.I think that you have to hold it before. (And I would recommend you to use CtrBootManager9 instead.)
--------------------- MERGED ---------------------------
Are you sure that you're using the correct firmware90.bin ? And is your sysNAND functional, at least?
How can you set it to boot straight into emunand?To clarify!
Like stated in the OP
When you boot straight into sysnand, it boots you into sysnand with firmware.bin, this is NOT firmware90..bin
Hold L then power on your system, will boot you into Emunand with firmware90.bin -> YOU DO need an Emunand on FW 9.0/9.2 NOT higher or you will get black screens
Hold R then power on your system, will boot you into Emunand with firmware.bin
When you boot straight into emunand, it boots you into emunand with firmware.bin, this is NOT firmware90..bin
Hold L then power on your system, will boot you into Sysnand with firmware90.bin -> YOU DO need a Sysnand on FW 9.0/9.2 NOT higher or you will get black screens
Hold R then power on your system, will boot you into Sysnand with firmware.bin
To clarify!
Like stated in the OP
When you boot straight into sysnand, it boots you into sysnand with firmware.bin, this is NOT firmware90..bin
Hold L then power on your system, will boot you into Emunand with firmware90.bin -> YOU DO need an Emunand on FW 9.0/9.2 NOT higher or you will get black screens
Hold R then power on your system, will boot you into Emunand with firmware.bin
When you boot straight into emunand, it boots you into emunand with firmware.bin, this is NOT firmware90..bin
Hold L then power on your system, will boot you into Sysnand with firmware90.bin -> YOU DO need a Sysnand on FW 9.0/9.2 NOT higher or you will get black screens
Hold R then power on your system, will boot you into Sysnand with firmware.bin
Using things like Decrypt9.My actual setup is updatedsysnand flag, so i coldboot sysnand 9.2 my L boots the firmware90.bin on emunand and R firmware.bin emunand, my SELECT boots HBL and START ctrboot manager but im missing from L firmware90 patched emunand since it only works on 9.0-9.2. i fast switch NANDs by going settings (and exiting while: ), pressing A boots to sysnand and pressing R+A boots emunand, the first emunand->sys the second to sys->emu
The thing, im unable to boot firmware90.bin, does it matter? (i dont know the actual diference between the normal firmware and the 90,) by the
"If you hold L on boot, emuNAND will be booted with the firmware90.bin on the SD card so you can use exploits (you need to create a 9.0/9.2 emuNAND for this!)."
what exactly are "exploits"?
Dumb question but i'm a bit confused
Oh thanks Mrraou, that probably explains why i was being kicked from loading emunand9 on HBL (i was trying to make a new emunand since stupid of me, installed A9LH without having an emunand setup [somehow i deleted it in the process or whatever lol])Using things like Decrypt9.
You don't need an emuannd setup, it boots it from the /rei folder. Holding down L or R whilst/before booting will send you into emunand.Oh thanks Mrraou, that probably explains why i was being kicked from loading emunand9 on HBL (i was trying to make a new emunand since stupid of me, installed A9LH without having an emunand setup)
Ohhhh right, I read the OP but this completely went over my head. Thanks!@ExodusTime I editted my preious post, see under [EDIT]
@TheDuckMan64 You really should read the OP descent and going a bit through the thread.
But to answer your question:
- Since i your question is to boot emunand, i assume you did read somewhere up on creating an empty file in the rei folder, called updatesysnand, i suppose you created this file already cause you boot straight into AuReiNand sysnand
- Remove this file or rename it to whatever, this will boot you into emunand instead of sysnand.
You don't need an emuannd setup, it boots it from the /rei folder. Holding down L or R whilst/before booting will send you into emunand.
The whole problem was that i had sysnand and emunand on 9.2 before A9LH, after installing it, i went to sleep (so i forgot how the fuck my emunand disappeared or whatever) i was trying to boot with R or L but i was getting black screen. So i figured i didn't have any emunand setup, only sysnand. i was trying to open decrypt9 or emunand9 from HBL but it was kicking me out. i finally solved it by putting decrypt9.bin as a9lh.bin and cloning sysnand to (the probably unexisting) emunand to lastly update it to 10.6. btw i don't have any problem nor doubtYou don't need an emuannd setup, it boots it from the /rei folder. Holding down L or R whilst/before booting will send you into emunand.
Can you share your build ? Please.This works great @Aurora Wright , I modified the code to have no splash screen and disabled the alternate L/R inputs for a pure sysNand boot build (with no accidental presses), so far really like the speed and how it's identical to an OEM boot.
I have no emunand on my sd card, but I can still boot it by holding down L/R (I have the updated sysnand file)If you don't have an emunand setup, the change of booting from emunand by holding L or R is equal to 0
My actual setup is updatedsysnand flag, so i coldboot sysnand 9.2 my L boots the firmware90.bin on emunand and R firmware.bin emunand, my SELECT boots HBL and START ctrboot manager