- Joined
- May 15, 2006
- Messages
- 878
- Trophies
- 1
- Age
- 36
- Location
- Bize Her Yer Trabzon
- Website
- www.HtheB.com
- XP
- 3,114
- Country
ah yes the 2DS....The 2ds would like to have a word with you young man.
Never thought people actually use them
ah yes the 2DS....The 2ds would like to have a word with you young man.
ah yes the 2DS....
Never thought people actually use them
What is the minimum fw that you have to be to gain access to the browser exploit?Pretty sure the N3DS can't be downgraded either.
From my understanding it can be with the newest Gateway update. When I was dumping the ROM it gave me the option to downgrade.Pretty sure the N3DS can't be downgraded either.
From my understanding it can be with the newest Gateway update. When I was dumping the ROM it gave me the option to downgrade.
I read his post wrong. Didn't catch the N before N3DS.There is no lower fw for N3DS then 8.X
So you CAN'T downgrade to 4.X
Also: Gateway doesn't support the N3DS yet.... !
If you only want this to update emunand, why not just update emunand to 9.5 online?
i was actually thinking about that earlier, like how would they manage the n3ds cart updates, guess the new3ds will use both partition 6 & 7, taking the shared assets from 7, and the n3ds specific titles from #6 as #6 is only 1MBThere's more to this rom than meets the eye (new3ds specific partition added):
http://www.3dbrew.org/wiki/System_Update_CFA#New3DS
(yellows8 just committed that)
*look at #6
View attachment 15725
a) I prefer to keep emunand offline
b) Nice to have a known working update that's recent and with themes, the last version that supports all of the recently published exploits (e.g. say Nintendo releases 9.6 and gateway disappears)
I would think that actually the new3ds would only look at it's own partition given it starts out at a much higher base firmware (9.0) that the old3ds. The old3ds partition, on the other hand, potentially needs to upgrade a 1.0 system, hence the much bigger partition size from all the changed titles.i was actually thinking about that earlier, like how would they manage the n3ds cart updates, guess the new3ds will use both partition 6 & 7, taking the shared assets from 7, and the n3ds specific titles from #6 as #6 is only 1MB
possibly i suppose on cart updates only update the essentials, but still 1MB seems awfully small ......actually i suppose its a US rom so it would only be the update from 9.0->9.2 ....so yeah 1MB is probably right, if it was JPN i suppose it would be bigger to cater for the changes from 8.1->9.2I would think that actually the new3ds would only look at it's own partition given it starts out at a much higher base firmware (9.0) that the old3ds. The old3ds partition, on the other hand, potentially needs to upgrade a 1.0 system, hence the much bigger partition size from all the changed titles.
if you had the cart sure, but if your using a rom, be prepared for a brick.....not saying it will, but several people where bricked updating to 8.1+ while in gateway modeI vaguely remember someone telling me that updating your SysNAND with a ROM would lead to a brick. Is that the case, or would we be able to update our SysNAND to 9.2.0 using this?
--new3ds--
Saving romfs\SNAKE\0004013820000002.cia... (new3ds NATIVE_FIRM)
Saving romfs\SNAKE\cup_list...
--old3ds--
Saving romfs\0004001000021000.cia...
Saving romfs\0004001000021100.cia...
Saving romfs\0004001000021f00.cia...
Saving romfs\0004001b00010702.cia...
Saving romfs\0004001b00010802.cia...
Saving romfs\0004003000008a02.cia...
Saving romfs\0004003000008f02.cia...
Saving romfs\0004003000009002.cia...
Saving romfs\0004003000009202.cia...
Saving romfs\0004003000009302.cia...
Saving romfs\0004003000009602.cia...
Saving romfs\0004003000009702.cia...
Saving romfs\000400300000c502.cia...
Saving romfs\000400300000c802.cia...
Saving romfs\000400300000c902.cia...
Saving romfs\000400300000cb02.cia...
Saving romfs\000400300000cc02.cia...
Saving romfs\000400300000cd02.cia...
Saving romfs\000400300000ce02.cia...
Saving romfs\0004009b00010402.cia...
Saving romfs\0004009b00010602.cia...
Saving romfs\0004009b00012302.cia...
Saving romfs\0004009b00013302.cia...
Saving romfs\000400db00010302.cia...
Saving romfs\000400db00010502.cia...
Saving romfs\000400db00017302.cia...
Saving romfs\0004013000001502.cia...
Saving romfs\0004013000001602.cia...
Saving romfs\0004013000001702.cia...
Saving romfs\0004013000001802.cia...
Saving romfs\0004013000001a02.cia...
Saving romfs\0004013000001b02.cia...
Saving romfs\0004013000001c02.cia...
Saving romfs\0004013000001d02.cia...
Saving romfs\0004013000001e02.cia...
Saving romfs\0004013000001f02.cia...
Saving romfs\0004013000002002.cia...
Saving romfs\0004013000002102.cia...
Saving romfs\0004013000002202.cia...
Saving romfs\0004013000002302.cia...
Saving romfs\0004013000002402.cia...
Saving romfs\0004013000002602.cia...
Saving romfs\0004013000002702.cia...
Saving romfs\0004013000002802.cia...
Saving romfs\0004013000002902.cia...
Saving romfs\0004013000002a02.cia...
Saving romfs\0004013000002b02.cia...
Saving romfs\0004013000002c02.cia...
Saving romfs\0004013000002d02.cia...
Saving romfs\0004013000002d03.cia...
Saving romfs\0004013000002e02.cia...
Saving romfs\0004013000002f02.cia...
Saving romfs\0004013000003102.cia...
Saving romfs\0004013000003202.cia...
Saving romfs\0004013000003302.cia...
Saving romfs\0004013000003402.cia...
Saving romfs\0004013000003502.cia...
Saving romfs\0004013000003702.cia...
Saving romfs\0004013000003802.cia...
Saving romfs\0004013000008002.cia...
Saving romfs\0004013800000002.cia...
Saving romfs\0004013800000003.cia...
Saving romfs\0004013800000102.cia...
Saving romfs\0004800f484e4841.cia...
Saving romfs\cup_list...
So what it seems here is that SSB is using additional space for updates?
3DSXL is only updated to 8.1 with this same card/rom?
N3DSXL/LL gets update to 9.2 with this same card/rom?
If all of the above is true than that might mean the additional features of the N3DSXL/LL might be able to be implemented into a 4.5 firmware. Kinda like rebuilding a windows 7 installation disk but with additional drivers to support new hardware