He already mentioned that he will provide a pre-compiled debian with removed drivers and all the unnecessary stuffs
great i will wait for that .... then i can help unbrick 3DS In france .....
He already mentioned that he will provide a pre-compiled debian with removed drivers and all the unnecessary stuffs
Yes, please! PM me a beta as soon as it's readyCurrently I'm working on getting an as small as possible raspian image done (780 MB atm) as my upstream speed sucks balls and i don't want to wait 20h for the upload to finish.
Tomorrow or wednesday I should receive my MMC card to "refine (a blatant euphemism for throw out of the window and rewrite) my code.
I've already taken wednesday to friday off (gotta burn some of my overhours anyway and this project is a good reason to finally do it.)
So there should be a not-yet-public beta version available soon and the public release soon+a bit longer (see what i did there, GW?).
Edit: if you'd be willing to participate in said closed beta I'll gladly send you the links.
bkiff is gonna release some intructions and his own kernel when the code is stable enough for end user use
could the same MOD be installed onto the 3DS, or is there not enough room in the guts. great work by the way..........................sudeki300
damn! i just need to comment on how nice that looks
Could you... talk in english ?si ont as pas de dump il reste l'emunand reccuperable avec emunand tool,j'ai fait comme sa pour une 3ds sans dump orig ,pour les sd non compatible dump sd avec testdisk-6.14.win pour avoir acces a la partition cachée,ouvrir hxd et changer 3DSCARDNAND en R4IGOLDNAND et le programme fonctionne et réccupere l'émununand
I have done backup for my 4.3 sysNAND and the 7.1 emuNAND.I think it is better to keep every version of the emuNAND you use.Who knows what will happen in the futureple666:
you can use EmuNAND_tool only if you kept a copy of your 4.x emuNAND.
Most users used emuNAND to update to 7.x, I don't know if everyone keep a backup from each NAND version.
Great news! It also looks like these are the same pins used for dumping your nand (except dat3, which you do not need for that function). Someone should make a commercial product for the 3ds XL that allows for easy dump/restore, unbricking, and extends the battery.
no you have to solder regardless of which method you useI was reading the instruction. so it's possible to unbrick without soldering and such by using raspberry pi? incredible.
If you are reading this your 3DS has most likely been bricked by a Virus called Gateway 3DS. If so return it and get a refund immediately.
Because what they have done is they made a soft-mod for the 3DS but then decided that they would earn more money if they added their own AP.
They also added a lot of obfuscation (to prevent pirates from pirating their card and software), which most likely also is the reason why some versions are not stable (and the brick code is triggered). And as you already see on your 3DS they added brick code in the 2.0_2b Version. This brick code is not even written correctly (else this unbricker wouldn't work). So they even failed at programming brick code.
To sum it all up you bought a badly programmed Virus.
Buy your games, don't pirate them. You see what happens when you pirate. I hope you learned from your mistake.
uint8_t CID_buffer[CID_length];
CID_buffer = read_CID(eMMC);
CID = AES_encrypt(CTR , GW_MASTERKEY, CID, CID_length ); //this is equivalent to CID = CID xor AES_encrypt(CTR , GW_MASTERKEY, 0x0, CID_length);
CID[0] = 5; //bit 0 and 2 set, meaning "set password" and "lock eMMC", for the unlock it's CID[0] = 2; //bit 1 set meaning "clear password" (unlock happens implicit)
CID[1] = 14; //next 14 bytes are the password
SD_command(eMMC, 42, CID, CID_length); //command 42 (lock/unlock) on the eMMC sending 16 bytes starting from &CID as data payload