Hs anyone with a brick from using clone firmware been able to take their sysnand dumped with the launcher been able to do the hardware mod and restore their system or is the brick unrecoverable?
Hacking Has anyone with a brick been able to recover?
- Thread starter Quicksilver88
- Start date
- Views 40,089
- Replies 202
Is this even a solvable problem? It'll probably take 1000s of geniuses at NSA to figure out how to undo what gateway has done.
I'm sure the government could crack it in less than a minute if they wanted to.
Of course they could, NSA probably has back-door access
- Joined
- Nov 13, 2008
- Messages
- 1,608
- Trophies
- 1
- Age
- 29
- Location
- Your house
- Website
- youtek.net
- XP
- 1,221
- Country
Not yet done.
There're 3 options to figure it out tho.
1. Reverse engineer the BETA with bricking code, to figure out what the bricking code does and make a backup of that particular section (if it erases something on nand. Could be bootrom chip as well)
2. Swap mainboards, effectively losing everything that was on your 3DS
3. Luck. Pure luck.
There're 3 options to figure it out tho.
1. Reverse engineer the BETA with bricking code, to figure out what the bricking code does and make a backup of that particular section (if it erases something on nand. Could be bootrom chip as well)
2. Swap mainboards, effectively losing everything that was on your 3DS
3. Luck. Pure luck.
isn't bootroom.-.. rom media?
anyway, I once formatted my 3DS to NTFS (with nand mod) to test stuff with it.
Yes, and I did use Panasonic SD formatter (2.0) to recreate block & page atributes from sd controller. then after drive shown, simply win32diskimager to restore nand.
(don't do it if you're not bricked, or you're not twisted).
anyway, I once formatted my 3DS to NTFS (with nand mod) to test stuff with it.
Yes, and I did use Panasonic SD formatter (2.0) to recreate block & page atributes from sd controller. then after drive shown, simply win32diskimager to restore nand.
(don't do it if you're not bricked, or you're not twisted).
I also thought about the possibility of using the Panasonic formatter, as it can uncorrupt devices with wrong storage size, but the problem doesn't seem to be that simple as one would like it to be. The only solution would be reprogramming the eMMC somehow.
Ultimately, there is no good reason why it should be even possible to brick the device in this way. Kind of reminiscent of Intel nics being brickable through software in Linux kernel 3.0.
What is the potential use case for Nintendo for being able to reprogram the emmc controller to report a zero length device?
What is the potential use case for Nintendo for being able to reprogram the emmc controller to report a zero length device?
There was this talk about SD card exploitation von the 30c3 this year.
I only watched it a bit, but they mentioned that SD card manufactuers are capable to define the size of the SD cards even if they are physically bigger .... there is a certain tolerence with SD cards at manufacturing stages, where they develop a 16 GB card for example, but only 4GB of those work ... so they sell you a 4GB card.
And there was a certain tool at this talk they mentioned, which is capable to alter the size of a SD card by messing with its internal controller.
Here is the talk (at the correct timecode):
And here is the tool they are talking about:
Site: http://www.drv5.cn/sfinfo/2698.html
DL Link: http://www.drv5.cn/sfinfo/download.asp?softid=2698&downid=12&id=4440
Mirror: http://www.drv5.cn/sfinfo/download.asp?softid=2698&downid=10&id=4441
This probably won't work, but who the hell knows, maybe we are lucky for once
Regards,
iCEQB
I only watched it a bit, but they mentioned that SD card manufactuers are capable to define the size of the SD cards even if they are physically bigger .... there is a certain tolerence with SD cards at manufacturing stages, where they develop a 16 GB card for example, but only 4GB of those work ... so they sell you a 4GB card.
And there was a certain tool at this talk they mentioned, which is capable to alter the size of a SD card by messing with its internal controller.
Here is the talk (at the correct timecode):
Code:
http://youtu.be/CPEzLNh5YIo?t=18m31sAnd here is the tool they are talking about:
Site: http://www.drv5.cn/sfinfo/2698.html
DL Link: http://www.drv5.cn/sfinfo/download.asp?softid=2698&downid=12&id=4440
Mirror: http://www.drv5.cn/sfinfo/download.asp?softid=2698&downid=10&id=4441
This probably won't work, but who the hell knows, maybe we are lucky for once
Regards,
iCEQB
That flashing tool is only for Appotech AX211 SD card controllers (http://osvdb.org/show/osvdb/101572). From what I read, 3DS uses a samsung NAND chip, maybe its posible to reflash the emmc controller somehow, samsung already did that one time on android when some of the eMMC controllers firmware were having several problems which lead to phones getting bricked.
there are many factors that SDIO can be affected, one i'm aware modern SD controllers allow shutting down clock the (clk) line. (will return in 00000000).
if what temper bud inian said is true, we may need to re-calculate emmc size, recreate file allocation table, then properly write such values directly to emmc.
I'll see if I can try bricking one of my microsd cards this way..
if what temper bud inian said is true, we may need to re-calculate emmc size, recreate file allocation table, then properly write such values directly to emmc.
I'll see if I can try bricking one of my microsd cards this way..
Similar threads
- Solved
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
@BakerMan, iirc it was about a news article about princess peach showtime using the word "sus" unironically -
-
-
-
-
-
-
-
-
-
-
-
-
@
realtimesave:
Nintendo needs to release a new console, switch is getting such shitty little games lately lol it's pathetic -
-
-
