As a member of a dying breed (emuNAND user) I am interested to how 11.0.0-33 affects updated sysNAND users accessing eshop online.
Hacking Luma3DS - Noob-proof 3DS Custom Firmware
- Thread starter Aurora Wright
- Start date
- Views 2,546,315
- Replies 19,840
- Likes 261
- Status
Just upgrade Luma to the latest commit (since friends module was changed), you should be fine
Yup. 11.0.0-33 just came out. Link: http://en-americas-support.nintendo.com/app/answers/detail/a_id/231/~/system-menu-update-history
well lets update and see what fucks up XD
--------------------- MERGED ---------------------------
just updated and its fine. just have to rename the hbl payload until one gets put out. loaded eshop and nothing got removed(some people wondered about shit with tickets). have not tried to install a ticket yet though.
OK, just to double check, I went through the EmuNAND_original.bin and SysNAND_original.bin on my O3DS XL that had never been updated. EmuNAND had 00000016.app ONLY. SysNAND had 0000000f.app ONLY. SysNAND.bin from after restoring EmuNAND via the "Keep A9LH" had 0000000f.app ONLY. There were not two files installed at any point in the process.
The fact remains that only one of the three units in question even had the two file issue. And on the one that did, the old file was 0000000f.app, not 00000012.app (TWL_FIRM 4.0, not TWL_FIRM 4.5). Yes, I actually went and installed the 4.5 TWL_FIRM rather than make any assumptions. You can keep being defensive and insisting that "only GW can do that" if you want, but 4.5 uses a completely different file, so the facts don't agree.
EDIT: OK, I'm not beyond admitting I was wrong. I checked the NAND backups, and both files are on both. And I just remembered the US downgrade file does go to 4.2 not 4.5. So, that one may indeed suffer GW corruption. But it was not the primary issue here.
@Aurora Wright, would it just kill you to admit that something broke old TWL_FIRM compatibility? No one's perfect. You assumed that the problem was a downgrade that I never even performed on one of the devices in question. You should know me better by now. I'm an expert. I don't make the simple mistakes (I go straight for the grand fallacy
). For the vocabulary/humor challenged, I just said I screw up big time, so don't take it as acting elitist. The real problem was that the old TWL_FIRM file was left on the device (presumably by Decrypt9) instead of being replaced. Something I was not aware of. I'll report it to d0k3 and see what he says (and there's a good chance he's already fixed it by now, knowing how fast he works, but just to be sure).
However, what complicated the issue was that old TWL_FIRM versions are either no longer supported or break something. THAT was the reason 5.2 had worked and 5.4 had stopped. It's not like I need you to fix it. I just needed to know the actual cause, so that I can proceed to update devices for other people without having to worry about getting angry phone calls. While your solution did work, it did not correctly explain why it worked. If you want to keep ignoring me, go right ahead. I'm just posting this so that the next guy with an un-downgraded 3DS that gets told he has a downgrader issue isn't left scratching his head.
My apologies if my posts "exhaust" you. I'm not trying to bug you, I'm trying to help you by providing accurate, scientifically derived information. Whether you want to use it or not is your call. I'll go talk to d0k3 now. He reads my feedback with an open mind, instead of going into defense mode. Good day.
The fact remains that only one of the three units in question even had the two file issue. And on the one that did, the old file was 0000000f.app, not 00000012.app (TWL_FIRM 4.0, not TWL_FIRM 4.5). Yes, I actually went and installed the 4.5 TWL_FIRM rather than make any assumptions. You can keep being defensive and insisting that "only GW can do that" if you want, but 4.5 uses a completely different file, so the facts don't agree.
EDIT: OK, I'm not beyond admitting I was wrong. I checked the NAND backups, and both files are on both. And I just remembered the US downgrade file does go to 4.2 not 4.5. So, that one may indeed suffer GW corruption. But it was not the primary issue here.
@Aurora Wright, would it just kill you to admit that something broke old TWL_FIRM compatibility? No one's perfect. You assumed that the problem was a downgrade that I never even performed on one of the devices in question. You should know me better by now. I'm an expert. I don't make the simple mistakes (I go straight for the grand fallacy
). For the vocabulary/humor challenged, I just said I screw up big time, so don't take it as acting elitist. The real problem was that the old TWL_FIRM file was left on the device (presumably by Decrypt9) instead of being replaced. Something I was not aware of. I'll report it to d0k3 and see what he says (and there's a good chance he's already fixed it by now, knowing how fast he works, but just to be sure).However, what complicated the issue was that old TWL_FIRM versions are either no longer supported or break something. THAT was the reason 5.2 had worked and 5.4 had stopped. It's not like I need you to fix it. I just needed to know the actual cause, so that I can proceed to update devices for other people without having to worry about getting angry phone calls. While your solution did work, it did not correctly explain why it worked. If you want to keep ignoring me, go right ahead. I'm just posting this so that the next guy with an un-downgraded 3DS that gets told he has a downgrader issue isn't left scratching his head.
My apologies if my posts "exhaust" you. I'm not trying to bug you, I'm trying to help you by providing accurate, scientifically derived information. Whether you want to use it or not is your call. I'll go talk to d0k3 now. He reads my feedback with an open mind, instead of going into defense mode. Good day.
Last edited by Kazuma77,
OK, just to double check, I went through the EmuNAND_original.bin and SysNAND_original.bin on my O3DS XL that had never been updated. EmuNAND had 00000016.app ONLY. SysNAND had 0000000f.app ONLY. SysNAND.bin from after restoring EmuNAND via the "Keep A9LH" had 0000000f.app ONLY. There were not two files installed at any point in the process.
The fact remains that only one of the three units in question even had the two file issue. And on the one that did, the old file was 0000000f.app, not 00000012.app (TWL_FIRM 4.0, not TWL_FIRM 4.5). Yes, I actually went and installed the 4.5 TWL_FIRM rather than make any assumptions. You can keep being defensive and insisting that "only GW can do that" if you want, but 4.5 uses a completely different file, so the facts don't agree.
Just admit it, @Aurora Wright, you gave the wrong advice. It happens. None of us know everything. You assumed that the problem was a downgrade that I never even performed on one of the devices in question. You should know me better by now. I'm an expert. I don't make the simple mistakes (I go straight for the grand fallacy
However, what complicated the issue was that you removed support for old TWL_FIRM versions without telling anyone. THAT was the reason 5.2 had worked and 5.4 had stopped. I don't care that it got removed. I just needed to know the actual cause, so that I can proceed to update devices for other people without having to worry about getting angry phone calls. While your solution did work, it did not correctly explain why it worked. If you want to keep ignoring me, go right ahead. Your acknowledgement is not required. I have the info I need. I'm just posting this to help others facing similar issues.
My apologies if my posts "exhaust" you. I'm not trying to bug you, I'm trying to help you by providing accurate, scientifically derived information. Whether you want to use it or continue in denial mode is your call. I'll go talk to d0k3 now. He reads my feedback with an open mind, instead of going into defense mode. Good day.
might want to quit while you're ahead because you sound like a douche
OK, just to double check, I went through the EmuNAND_original.bin and SysNAND_original.bin on my O3DS XL that had never been updated. EmuNAND had 00000016.app ONLY. SysNAND had 0000000f.app ONLY. SysNAND.bin from after restoring EmuNAND via the "Keep A9LH" had 0000000f.app ONLY. There were not two files installed at any point in the process.
The fact remains that only one of the three units in question even had the two file issue. And on the one that did, the old file was 0000000f.app, not 00000012.app (TWL_FIRM 4.0, not TWL_FIRM 4.5). Yes, I actually went and installed the 4.5 TWL_FIRM rather than make any assumptions. You can keep being defensive and insisting that "only GW can do that" if you want, but 4.5 uses a completely different file, so the facts don't agree.
Just admit it, @Aurora Wright, you gave the wrong advice. It happens. None of us know everything. You assumed that the problem was a downgrade that I never even performed on one of the devices in question. You should know me better by now. I'm an expert. I don't make the simple mistakes (I go straight for the grand fallacy
However, what complicated the issue was that you removed support for old TWL_FIRM versions without telling anyone. THAT was the reason 5.2 had worked and 5.4 had stopped. I don't care that it got removed. I just needed to know the actual cause, so that I can proceed to update devices for other people without having to worry about getting angry phone calls. While your solution did work, it did not correctly explain why it worked. If you want to keep ignoring me, go right ahead. Your acknowledgement is not required. I have the info I need. I'm just posting this to help others facing similar issues.
My apologies if my posts "exhaust" you. I'm not trying to bug you, I'm trying to help you by providing accurate, scientifically derived information. Whether you want to use it or continue in denial mode is your call. I'll go talk to d0k3 now. He reads my feedback with an open mind, instead of going into defense mode. Good day.
Even if your reasoning here is totally sound and you are completely right (of which I have no idea if that's the case or not), your attitude in handling this interaction with a developer who does nothing but work to benefit the community (for free!) is atrocious.
Your accusatory phrasing and completely ridiculous statements such as "I don't make the simple mistakes" give off an atmosphere of nothing but entitlement.
If you had handled this responsibly or treated @Aurora Wright with respect, this would be a different story, but as far as I am concerned, for now, you can take this attitude of yours and shove it up your ass.
Last edited by Plailect,
Decrypt9 can't mount CTRNAND, let alone write files which don't already exist. Restoring NAND is an operation with raw encrypted data, not at the filesystem level. @d0k3 can confirm that to you!OK, just to double check, I went through the EmuNAND_original.bin and SysNAND_original.bin on my O3DS XL that had never been updated. EmuNAND had 00000016.app ONLY. SysNAND had 0000000f.app ONLY. SysNAND.bin from after restoring EmuNAND via the "Keep A9LH" had 0000000f.app ONLY. There were not two files installed at any point in the process.
The fact remains that only one of the three units in question even had the two file issue. And on the one that did, the old file was 0000000f.app, not 00000012.app (TWL_FIRM 4.0, not TWL_FIRM 4.5). Yes, I actually went and installed the 4.5 TWL_FIRM rather than make any assumptions. You can keep being defensive and insisting that "only GW can do that" if you want, but 4.5 uses a completely different file, so the facts don't agree.
Just admit it, @Aurora Wright, you gave the wrong advice. It happens. None of us know everything. You assumed that the problem was a downgrade that I never even performed on one of the devices in question. You should know me better by now. I'm an expert. I don't make the simple mistakes (I go straight for the grand fallacy
However, what complicated the issue was that you removed support for old TWL_FIRM versions without telling anyone. THAT was the reason 5.2 had worked and 5.4 had stopped. I don't care that it got removed. I just needed to know the actual cause, so that I can proceed to update devices for other people without having to worry about getting angry phone calls. While your solution did work, it did not correctly explain why it worked. If you want to keep ignoring me, go right ahead. Your acknowledgement is not required. I have the info I need. I'm just posting this to help others facing similar issues.
My apologies if my posts "exhaust" you. I'm not trying to bug you, I'm trying to help you by providing accurate, scientifically derived information. Whether you want to use it or continue in denial mode is your call. I'll go talk to d0k3 now. He reads my feedback with an open mind, instead of going into defense mode. Good day.
. I just inverted the .app logic (newest to oldest) to support a valid/intended behavior (background partial updates) instead of GW crap, didn't remove any support.Also, you're nothing more than a troll and this was made obvious from your very first post.
hey remember i cant use the browser? even updating i have the same error rip browser btw how i rename the payload?
put the sd card in your pc and rename it just change the firm numbering in in the name
soguys so far im on step 4 on 11 If you encounter an error at any point during the downgrade, restore your RedNAND backup from emuNAND_formatted.bin using OTPHelper through the Homebrew Menu on SysNAND. Afterwards, you can retry the downgrade on RedNAND, restoring from backup whenever it fails until it goes through successfully. This downgrade process can take many many tries in some situations, just keep trying until it works
So far it happen 4th time now... is this known to happen?
here's were it errors at each time... http://prntscr.com/b282e2
6th time now something has to be mess up?
So far it happen 4th time now... is this known to happen?
here's were it errors at each time... http://prntscr.com/b282e2
6th time now something has to be mess up?
Last edited by gordesky1,
Attitude? That was a joke. Definition of an expert -- one who avoids the simple mistakes while sweeping on towards the grand fallacy. Perhaps you lack an understanding of the concept of humor? Since you're here, your guide could use some work. All that mention of RedNAND is confusing. Why have people create a non-GW-compatible RedNAND when you're just going to have them erase it? Gateway owners, who do need to keep EmuNAND around, need it to be a regular one.
Anyway, she was blowing me off like I was some noob that hadn't read the FAQ or something, and completely ignoring any facts I presented that countered her assumptions.
Decrypt9 can't mount CTRNAND, let alone write files which don't already exist. Restoring NAND is an operation with raw encrypted data, not at the filesystem level. @d0k3 can confirm that to you!
Also, you're nothing more than a troll and this was made obvious from your very first post.
I don't claim to know how the restoration process works. I only know that 4.5 uses 00000012.app and not 0000000f.app. And that manually installing a lower TWL_FIRM would have erased any remnants of a GW downgrade. So, your assumption does not hold up.
Also, 0000000f.app was ALL that was on two of these. There was no 00000016.app present. 5.2 worked with them. 5.4 did not until I installed the new version. So, something got removed/altered that affected compatibility. I will not join in the name-calling. What you think of me is irrelevant. I've said what I had to say. I still consider your CFW the finest around, was not attacking it in any way, and was merely trying to help. I don't know why you get so defensive.
Last edited by Kazuma77,
@Aurora Wright hey a few days ago @pbanj and i tried to fix i issue i have in my new 3ds i can open the browser even deleting the app with fbi and update the 3ds it´s a bug of my 3ds not of your cfw but maybe you could help me out pls
edit: i forgot to put the issue xD i cant open the browser it just gave me and error (the same as browser hax gave when it fails)
edit: i forgot to put the issue xD i cant open the browser it just gave me and error (the same as browser hax gave when it fails)
Last edited by alex61194,
- Status
Similar threads
-
- Poll
- No one is chatting at the moment.
-
-
-
-
-
-
-
@ x65943:
If your throat closes, putting oxygen in your mouth will not solve anything - as you will be introducing oxygen prior to the area of obstruction -
-
You either need to be intubated to bypass obstruction or create a stoma inferior to the the area of obstruction to survive
-
-
-
-
-
-
-
-
@
JuanMena:
It was waiting for you to order another one.
Seems like, your PSU was waiting for a partner. -
-
-
-
-
-
-
-
