for some reason everything works fine for me with the latest 4.1 and it is 3 seconds faster for me booting into emuNAND.
thanks Aurei </3
thanks Aurei </3
Yes, it's really blocked from system update I confirmed 2 times.Guys really a quick question, I have AuReiNand installed and I'm asking if there is a way to check that FIRM partitions are really blocked. I would not like to update sysnand and lose a9lh for a mistake that I eventually made.
Thank you.
Sorry if I sounded rude, it's because I actually receive so many requests for help...I did exactly the same thing, it always freezes at "Copied FIRM".
Same build with same firmware.bin works fine with AuReiNand v3.11.
It's not just me, two people already confirmed they got same result.
I have O3DS, if that's important, but I'm not sure about others.
I am really sorry for bothering you. Usually I'm trying not to ask for anything,
but I just really don't know what can possibly be wrong here…
Thank you for your effort anyway. And thank you even more for all your hard work.
It's working now. (Cakes_152 A9LH)Sorry if I sounded rude, it's because I actually receive so many requests for help...
Anyway I've confirmed it, and there was actually a problem (the ARM11 was in an infinite loop waiting for a function to be passed to it, but since Cakes and the other payloads use the same space in FCRAM as AuReiNand, the infinite loop ended up being overwritten lol (I was dumb not to realize this beforehand). Now I have separated the ARM11 screen init code from the AuRei main code and I copy it just after the chainloader. So no payload overwrites it. Now ARM11 access works for payloads, tested cakes and it works.
http://www105.zippyshare.com/v/8Ubd9Zk2/file.html
Thank you, everything works perfect now!Sorry if I sounded rude, it's because I actually receive so many requests for help...
Anyway I've confirmed it, and there was actually a problem (the ARM11 was in an infinite loop waiting for a function to be passed to it, but since Cakes and the other payloads use the same space in FCRAM as AuReiNand, the infinite loop ended up being overwritten lol (I was dumb not to realize this beforehand). Now I have separated the ARM11 screen init code from the AuRei main code and I copy it just after the chainloader. So no payload overwrites it. Now ARM11 access works for payloads, tested cakes and it works.
http://www105.zippyshare.com/v/8Ubd9Zk2/file.html
A is not a valid key to launch payloads with. Neither is B.I am having a problem in getting uncart to work with the aureinand boot manager. I've placed the uncart.bin in the payloads folder and renamed it to a.bin. Alongside uncart I've also got emunand9 and decrypt9 renamed respectively to default.bin and y.bin. Those last two, work perfectly on boot and they'll launch when I press the appropriate button combination.
However, I can't get uncart.bin to work. When I try to launch it (L+A) at boot, it will complain that aurei/firmware(90).bin is missing. Though, I do have the appropriate firmware.bin in the aurei folder. How can I fix this?
Any speed difference?
The problem with arm9select is that some buttons interfere with AuRei functions (both use buttons for stuff). The aurei loader (which is, basically, a stripped down arm9select) only allows the payloads whose buttons don't interfere with anything.Use arm9select it takes priority over built in AuReiNand loader.
I suppose I need to explain what I just said. Suppose you're soft rebooting and you need to hold A to override the forced boot. Or, suppose that you need to hold R+B to launch the second emuNAND. Of course you can't assign R, B or A to arm9select (same for L, and Select too). Now, with the built-in loader I can change the order of stuff to allow you to have an "R" payload and a "Select" one (which you can't have with arm9select!). I can also not include the other buttons (B, A) which would interfere with AuRei.That is why I fell in love with AuReiNand's earlier releases when the loader.vin was separate. That way I could delete it and have no conflict with arm9select.
I suppose I need to explain what I just said. Suppose you're soft rebooting and you need to hold A to override the forced boot. Or, suppose that you need to hold R+B to launch the second emuNAND. Of course you can't assign R, B or A to arm9select (same for L, and Select too). Now, with the built-in loader I can change the order of stuff to allow you to have an "R" payload and a "Select" one (which you can't have with arm9select!). I can also not include the other buttons (L, R, B, A) which would interfere with AuRei.
I think the main benefits are the slightly smaller size. Makes backups and restores take a bit lesswell i did convert my NANDs using d9, from GW emuNAND into redNAND.
speed difference is maybe 1-2seconds faster booting, but come on guys.
it is only 1-2 friggin seconds, are 8-12 seconds that much to wait for it to boot ? i think not, so i dont see the big benefit of that 'redNAND' thingie.
besides, whenever i think of menuhax i go very happy with a9lh+aurei , cause holysheep the bootrate/time is like day and night.(compared to menuhax..) xD
Do you think you could add support for the ZL and ZR buttons?x.bin, y.bin, select.bin, start.bin, right.bin, left.bin, up.bin, down.bin.
yeDownload new version and overwrite arm9loaderhax.bin in sd root only