Hacking Potential reason for random errors on N3DS after downgrading?

[dragonjud]

Thank you.
Interesting. I was looking at a different devmenu file, but I've matched your md5 elsewhere.

All done. Thanks again. After seeing Big Blue menu, DevMenu, and the other CIA installers, I'm not sure why folks like FBI. Sure it's minimalistic, and gets the job done, but deleting that Amiibo title was unnecessarily difficult because of that interface.

On another note, I don't think I'm going to downgrade my nice MM N3dsxl until Gateway or anybody else releases something a little more reliable. Sure I got it done with a lot of help, but it took too long, and almost bricked the system in the process (after taking all the precautions one can take).

 

[Doopl]

Checking installed titles..

Title ID 0x000400300000b902
Extra Title
Title ID 0X0004013000001b02
Expected Version 0X0800
Installed Version 0x0c01
Title ID 0x0004013000001a02
Expected Version 0x1400
Installed Version 0x1801
Complete.
Checking missung titles...
Complete
Press (A) to continue


Is this good or bad

9.2.0.E

I have the same results posted here, but I also have a second extra title:

0x0004000100177000

Searched the thread and couldn't find it mentioned anywhere. Any idea what it is, and whether it should be removed or just left alone?

 

[Frieren]

Sure I got it done with a lot of help, but it took too long, and almost bricked the system in the process (after taking all the precautions one can take).

It's hapenned because you downgraded from 9.x fw. Downgrading from 9.x is asking for brick. Most stories about incomplete downgrading started from words "i'm on 9.x fw and sysupdater failed in process". Downgrade data gathering: https://docs.google.com/spreadsheet...nrZGXBQeB-fC4q6mqd1Dk/htmlview#gid=1379123133 shows that success rate with 9.x fw are unacceptable low.
You should update 9.x to 10.3 with sysupdater first. And then downgrade to 9.2 It's still can cause a brick, of course. But chances are close to zero. 10.3 success rate are very high.
I updated to 10.3 more than 15 n3ds. And then successfully downgrade them all to 9.2. Don't have any problem at all. And here is guy, who downgraded 40 units: https://gbatemp.net/threads/i-have-...ed-about-40-o3ds-n3ds-heres-what-i-do.414688/ He updated them to 10.3 too.
Wondering why no one still don't made a sticky thread about success rate of downgrading 10.3 and 9.x. And people continued breacking their 9.x units.

 

[Shirako]

so i downgraded my n3dsxl from 10.3>9.2 and im missing a lot of files, it's an incomplete downgrade even the native firm isn't downgraded. I'm wondering if i should update to 10.3 first before downgrading again or can i just run sysupdater again? if i do have to, then how would i do it?

 

[FR0ZN]

It's hapenned because you downgraded from 9.x fw. Downgrading from 9.x is asking for brick. Most stories about incomplete downgrading started from words "i'm on 9.x fw and sysupdater failed in process". Downgrade data gathering: https://docs.google.com/spreadsheet...nrZGXBQeB-fC4q6mqd1Dk/htmlview#gid=1379123133 shows that success rate with 9.x fw are unacceptable low.
You should update 9.x to 10.3 with sysupdater first. And then downgrade to 9.2 It's still can cause a brick, of course. But chances are close to zero. 10.3 success rate are very high.
I updated to 10.3 more than 15 n3ds. And then successfully downgrade them all to 9.2. Don't have any problem at all. And here is guy, who downgraded 40 units: https://gbatemp.net/threads/i-have-...ed-about-40-o3ds-n3ds-heres-what-i-do.414688/ He updated them to 10.3 too.
Wondering why no one still don't made a sticky thread about success rate of downgrading 10.3 and 9.x. And people continued breacking their 9.x units.

Is there any tutorial how to upgrade a 9.5.0 N3DS to 10.3?

 

[Frieren]

Is there any tutorial how to upgrade a 9.5.0 N3DS to 10.3?

Don't know. But updating process is identical to downgrading. You can follow this guide: https://gbatemp.net/threads/simple-guide-to-downgrading-your-3ds.407888/
Just use proper 10.3 .cia pack for your region instead of 9.2 .cia pack. And in sysupdater you need to press A instead of Y.
Also, i, personally, use this version of sysupdater: http://sysupdater.gamescom.net/sysUpdater.zip

 

[FR0ZN]

Don't know. But updating process is identical to downgrading. You can follow this guide: https://gbatemp.net/threads/simple-guide-to-downgrading-your-3ds.407888/
Just use proper 10.3 .cia pack for your region instead of 9.2 .cia pack. And in sysupdater you need to press A instead of Y.
Also, i, personally, use this version of sysupdater: http://sysupdater.gamescom.net/sysUpdater.zip

Thank you, the right sysUpdater version is basically what I was looking for, because there were a shit ton of sysUpdater versions once memchunkhax2 showed up and I wouldn't know which to use because of mixed reports.

 

[GothicIII]

It's hapenned because you downgraded from 9.x fw. Downgrading from 9.x is asking for brick. Most stories about incomplete downgrading started from words "i'm on 9.x fw and sysupdater failed in process". Downgrade data gathering: https://docs.google.com/spreadsheet...nrZGXBQeB-fC4q6mqd1Dk/htmlview#gid=1379123133 shows that success rate with 9.x fw are unacceptable low.
You should update 9.x to 10.3 with sysupdater first. And then downgrade to 9.2 It's still can cause a brick, of course. But chances are close to zero. 10.3 success rate are very high.
I updated to 10.3 more than 15 n3ds. And then successfully downgrade them all to 9.2. Don't have any problem at all. And here is guy, who downgraded 40 units: https://gbatemp.net/threads/i-have-...ed-about-40-o3ds-n3ds-heres-what-i-do.414688/ He updated them to 10.3 too.
Wondering why no one still don't made a sticky thread about success rate of downgrading 10.3 and 9.x. And people continued breacking their 9.x units.

Interesting chart. This is also my speculation that 9.x downgrades fail. The problem is, I don't see any evidence that proves this as a fact. If you look carefully at the chart, more then (guessing here) ~6 of 8 downgrades from 9.x are successful. Also there are many reported bricks from 10.3 firmware.
The analytics page of the chart is s**t. The real interesting results are not parsed. In that state the chart except for n3ds vs o3ds is pretty useless because of the randomness of the data and missing input (like if it was a usererror or not when bricking).
I want it to be proven because I suffered the issue myself but if I try to explain it on another forum with this chart as evidence I will be taken as an idiot.
Maybe you can clarify this?

 

[Frieren]

Interesting chart. This is also my speculation that 9.x downgrades fail. The problem is, I don't see any evidence that proves this as a fact. If you look carefully at the chart, more then (guessing here) ~6 of 8 downgrades from 9.x are successful.
The analytics page of the chart is s**t. The real interesting results are not parsed. In that state the chart except for n3ds vs o3ds is pretty useless because of the randomness of the data and missing input (like if it was a usererror or not when bricking).
I want it to be proven because I suffered the issue myself but if I try to explain it on another forum with this chart as evidence I will be taken as an idiot.
Maybe you can clarify this?

Well, the only valid evidence is a statistics. And it seems that they deleted a lot reports from chart for some reason. When i watched this chart a couple of weeks ago there be a lot reports about 9.x n3ds breaks.
If you search on this forum last n3ds break reports, you can see that almost all of them related to fw version<10.3:
https://gbatemp.net/threads/safesysupdater-success-n3ds-frankenfirmware.417135/
https://gbatemp.net/threads/having-issues-after-downgrading-the-pokemon-n3ds.416960/
https://gbatemp.net/threads/downgrading-n3ds-on-9-6-to-9-2.416787/
https://gbatemp.net/threads/frankenfirmware-is-alive.415203/
https://gbatemp.net/threads/need-help-updating-n3ds-v9-9-0-26e-to-10-3.416012/ (This case is very revealing on many levels. He wanted update his 9.x 3ds to 10.3 But people persuaded him to downgrade from 9.x and don't update to 10.3. Voila, one more broken 9.x unit)
https://gbatemp.net/threads/new-3ds-using-9-9.412270/
etc.
Along with my personal experience this is enough proof for me.

Also there are many reported bricks from 10.3 firmware.

Yeah, first versions of sysupdater had a low success rate. And in case with this old versions it doesn't matter wich fw version you downgrade.
Situatuion with 9.x fw breaks related only to latest version of sysupdater and n3ds. I don't think this problem affects o3ds.

 

[FR0ZN]

@homuhomu I just want to thank you again, my buddy managed to update to 10.3 right now.
We had to fiddle with browserhax and menuhax ropbin payloads, because it wasn't accepting 9.5 payloads anymore, we had to use 9.2 payloads because of the failed downgrade yesterday which downgraded home menu to 9.2

And sysUpdater took like 100 tries to exploit ARM11

 

[[]KAOS[]Casey]

Just wanted to throw my two cents in:

I had a N3DS on 9.8.0-25, and used safesysupdater with 9.2.0-u-full package to downgrade. Entrypoint was ninjhax.

It failed and gave me a franken firmware of 9.2.0-25. Ninjhax was unable to boot back with no modifications to the payload, trying to enter the new "firmware" version did not work. It would look like it would launch, but the homebrew channel never actually started.

I fixed it by using oothax to install a 9.2.0-25 payload to the cart on a different 3ds; for some reason, oothax could boot the homebrew channel where ninjhax could not. Re-issuing safesysupdater fixed the problem, though it took several attempts for it to even start.

I knew about updating to 10.3 ahead of time, but I did not do so to save time. Placebo, I thought. The data does seem to be compelling otherwise...

 

[dragonjud]

Ended up with my second frankenfirm today. Was trying another N3ds from 9.6 to 9.2. Yes, I know there're those who still believe it's still better to update to 10.3. The reality is that you still have some cleanup to do, regardless of where you start.
A few differences to note this time:
1) After a few subsequent failures, the OOTHax payloads would launch HBL, but it would not successfully go into the HBL menu. In these instances, the only solution was to format the system (didn't really want to do it while in frankenfirm, but had no choice). Don't really know the reason for this (pure speculation that the notifications on a new menu were helping the process). Also attempted the SULib version of SysUpdater, but that seems buggier to me (recommend staying away).
As other have surmised, I think all these failures are rooted around the home menu title. Hope they figure out eventually. Not sure anybody is looking into this anymore. Some SafeSysupdater developers are looking for feedback, but since that program is actually worse (when coming from 9.x), I'm hesitant to even try.

2) Downgrade checker only shows one mismatch title (aside from the extra Amiibo title).

 

[BurningDesire]

[MISMATCHED VERSIONS]

TitleID          Vers: Expected Installed     Description



[EXTRA TITLES]

TitleID                Vers.     Description



[MISSING TITLES]

TitleID                Vers.     Description

0004003000008b02       00006     solv3 system-applet (Miiverse-posting applet)
0004013800000202       03665     AGB_FIRM
0004013800000102       08817     TWL_FIRM
0004013800000003       05632     SAFE_MODE_FIRM
0004013000008003       00000     SAFE_MODE NS system-module
0004013000003802       06144     act system-module
0004013000003702       05120     RO system-module
0004013000003502       06147     Notifications system-module
0004013000003303       00000     SAFE_MODE IR system-module
0004013000003203       00000     SAFE_MODE friends system-module
0004013000003103       00000     SAFE_MODE PS system-module
0004013000002f03       00000     SAFE_MODE SSL system-module
0004013000002e03       00000     SAFE_MODE Sockets system-module
0004013000002d03       05120     SAFE_MODE NWM system-module
0004013000002c03       00000     SAFE_MODE NIM system-module
0004013000002a03       00000     SAFE_MODE MP system-module
0004013000002903       00000     SAFE_MODE HTTP system-module
0004013000002703       00000     SAFE_MODE CSND system-module
0004013000002403       00000     SAFE_MODE AC system-module
0004013000002303       00000     SAFE_MODE spi system-module
0004013000002203       00000     SAFE_MODE PTM system-module
0004013000002103       00000     SAFE_MODE PDN system-module
0004013000001f03       00000     SAFE_MODE MCU system-module
0004013000001e03       00000     SAFE_MODE i2c system-module
0004013000001d03       00000     SAFE_MODE HID system-module
0004013000001c03       00000     SAFE_MODE GSP system-module
0004013000001b03       00000     SAFE_MODE GPIO system-module
0004013000001a03       00000     SAFE_MODE DSP system-module
0004013000001803       00000     SAFE_MODE Codec system-module
0004013000001703       00000     SAFE_MODE Config system-module
0004013000001503       00000     SAFE_MODE AM system-module
000400db00017302       09248     CVer
000400db00016302       00320     NVer
000400db00010502       14336     Nintendo Zone hotspot list CFA
000400db00010302       06144     NGWord bad word list CFA
0004009b00015302       00000     N/A
0004009b00014302       01024     TWN System Font CFA
0004009b00014202       01024     KOR System Font CFA
0004009b00014102       01024     CHN System Font CFA
0004009b00014002       00000     System Font CFA
0004009b00013302       04099     EULA CFA
0004009b00012302       09218     N/A
0004009b00011e02       00000     N/A
0004009b00011d02       00000     N/A
0004009b00011602       00000     N/A
0004009b00011402       00000     N/A
0004009b00010602       00002     Non-Nintendo TLS Root-CA Certificates CFA
0004009b00010402       04098     N/A
0004009b00010202       00000     Mii-data CFA
000400300000f602       02050     Miiverse memolib
000400300000ce02       08200     mint (eShop applet)
000400300000cd02       03073     extrapad applet
000400300000cc02       02048     SNOTE_AP
000400300000cb02       03075     PNOTE_AP
000400300000c902       02048     appletEd
000400300000c803       00000     SAFE_MODE Software Keyboard
000400300000c802       04096     Software Keyboard
000400300000c503       00000     SAFE_MODE error applet
000400300000c502       05128     error applet
000400300000bd02       02048     Miiverse applet
0004003000009702       04097     Notifications applet
0004003000009602       06144     Friend List applet
0004003000009402       04096     Internet Browser
0004003000009302       04096     Game Notes applet
0004003000009202       05120     Instruction Manual applet
0004003000009002       02049     Camera applet
0004003000008f02       12288     Home Menu
0004003000008a03       00000     SAFE_MODE ErrDisp
0004001b00018202       02050     N/A
0004001b00018102       01025     N/A
0004001b00018002       03078     N/A
0004001b00010802       00000     N/A
0004001b00010702       04096     NS CFA
0004001b00010002       00000     ClCertA
000400100002c000       02051     Nintendo Network ID Settings application
0004001000024000       02048     Promotional video application
0004001000021f00       02049     SAFE_MODE System Updater application
0004001000021e00       01040     AR Games
0004001000021d00       01040     Face Raiders
0004001000021b00       01034     Nintendo Zone application
0004001000021a00       05131     System Transfer application
0004001000021900       13321     eShop
0004001000021800       05136     StreetPass Mii Plaza
0004001000021700       02055     Mii Maker
0004001000021500       03088     Nintendo 3DS Sound application
0004001000021400       04097     Nintendo 3DS Camera application
0004001000021300       02051     Health and Safety Information
0004001000021200       02064     Activity Log
0004001000021100       03073     Download Play application
0004001000021000       08203     System Settings
0004800f484e4c41       00000     TWL Version Data
0004800f484e4841       11264     Nintendo DS Cart Whitelist
00048005484e4441       01024     Download Play (DS-mode application)
0004800542383841       02048     DS Internet (DSi-mode application)
0004013800000002       17120     NATIVE_FIRM
0004013000008002       14336     NS system-module
0004013000003402       11266     SpotPass system-module
0004013000003302       08192     IR system-module
0004013000003202       08192     friends system-module
0004013000003102       05120     PS system-module
0004013000002f02       07168     SSL system-module
0004013000002e02       07168     Sockets system-module
0004013000002d02       10240     NWM system-module
0004013000002c02       10249     NIM system-module
0004013000002b02       07169     NDM system-module
0004013000002a02       02048     MP system-module
0004013000002902       12288     HTTP system-module
0004013000002802       06145     Download Play system-module
0004013000002702       05120     CSND system-module
0004013000002602       10240     StreetPass system-module
0004013000002402       08192     AC system-module
0004013000002302       03072     spi system-module
0004013000002202       09219     PTM system-module
0004013000002102       02048     PDN system-module
0004013000002002       02048     Microphone system-module
0004013000001f02       08192     MCU system-module
0004013000001e02       03076     i2c system-module
0004013000001d02       09216     HID system-module
0004013000001c02       10240     GSP system-module
0004013000001b02       02048     GPIO system-module
0004013000001a02       05120     DSP system-module
0004013000001802       07168     Codec system-module
0004013000001702       12290     Config system-module
0004013000001602       09216     Camera system-module
0004013000001502       08192     AM system-module
0004003000008a02       07168     ErrDisp

Can someone tell me what that means?

Edit: I am on O3DS I just didn't want to make a new thread xD

 

[Deleted User]

Should post a list of titles you have installed from the checker. All that shows is like the entire firmware is missing.

 

[FR0ZN]

Can someone tell me what that means?

Edit: I am on O3DS I just didn't want to make a new thread xD

I'm actually amazed you could get into some sort of HBL to do this check for all those missing titles
I would put all those missing titles into one folder and install them all to NAND with FBI and redo the check.

 

[BurningDesire]

I'm actually amazed you could get into some sort of HBL to do this check for all those missing titles
I would put all those missing titles into one folder and install them all to NAND with FBI and redo the check.

I don't know where they are on that iso site. Any good search tips?

 

[FR0ZN]

They are in your downgrade pack ... your downgrade attempt failed to install those in the process.

 

[dragonjud]

Okay, So, downgraded another N3ds from 10.6 this time. I've checked all the mismatches, but not sure what to do with this title (not sure if I should just ignore it). It can be found in Old 3ds pack. the Any ideas?:

0004009b00010602 Non-Nintendo TLS Root-CA Certificates

I should note that this 3ds was not clean, and had tons of installed games (including Ironfall, and at least one GBA game)

 

[FR0ZN]

Okay, So, downgraded another N3ds from 10.6 this time. I've checked all the mismatches, but not sure what to do with this title (not sure if I should just ignore it). It can be found in Old 3ds pack. the Any ideas?:

0004009b00010602 Non-Nintendo TLS Root-CA Certificates

I should note that this 3ds was not clean, and had tons of installed games (including Ironfall, and at least one GBA game)

Replace all mismatched titles with the ones from the O3DS 9.2 downgrade pack from your region.

Extra titles can just be deleted.

Missing titles have to be installed by hand onto the NAND and should be taken from the N3DS downgrade pack this time.

 

[simbin]

Downgraded SysNand 10.6 > 9.2, using the new method.

Unlinked EmuNand and updated it to 10.6, SysNand is still 9.2.

When I ran SysCheck on SysNand I got the following:

Title ID 0x0004009b00010602
Expected version 0x0002
Installed version 0x0400
Title ID 0x0004003000009e02
Extra title
Title ID 0x0004013000001b02
Expected version 0x0800
Installed version 0x0c01
Title ID 0x0004013000001a02
Expected version 0x1400
Installed version 0x1801

From what I can tell the Extra title is just some Amiibo stuff but I don't know about the rest.

Any idea what the others are - should I try to fix them? Is EmuNand ok since I updated it back to 10.6?

I want to do the arm9loaderhax, but I'm afraid to go any further if this might cause a problem.
Thanks

UPDATE: The last 3 Titles, including the missing Amiibo Title are listed here as useless? Still not sure what they are. The first one I still can't find any info on.

https://github.com/JustPingo/KernelTimeMachine/blob/master/source/ttp.c
#define USELESS92AMOUNT (12) u64 uselessTitlesFor92[USELESS92AMOUNT] = { // Latest update: 10.3
0x0004001B00019002, 0x000400300000B902, 0x0004013000004002, 0x0004003000009502, 0x0004003000009E02, 0x0004001B00010802, 0x0004009B00010402, 0x0004013000001A02, 0x0004013000001B02, 0x0004800542383841, 0x00048005484E4441