Hacking Region Changing Palantine CFW

  • Thread starter Thread starter AquaX101
  • Start date Start date
  • Views Views 1,563
  • Replies Replies 5

AquaX101

Well-Known Member
Member
Joined
Apr 15, 2014
Messages
719
Reaction score
169
Trophies
1
Location
Somewhere
XP
1,095
Country
United States
For me its been about impossible region changing Palantine's CFW, I get stream error when I use one of the SecureInfo_A Injectors and I keep getting my 3ds frozen when I use the other one, And I also can't extract the emunand using emunand tool because it gives me a 1 KB emunand backup and an unknown nand size error. Has anyone been able to region change palantine cfw? I also don't own a GW so that's why I have to use palantine to install the system cias.
 
the difference between rednand and emunand is just one last dummy sector that rednand makes, to extract the rednand and make it a normal emunand, use the hex workshop to open the physical drive of ur SD! and save the sectors (from>2 to 1931264) that will get you a normal emunand.

also ive been trying to update with 3DNUS 9.2 cias pack but every time i convert the updated rednand to normal emunand i get brick when booting from rxTools, anyone knows a better way for me to update it???
 
  • Like
Reactions: codychaosx
the difference between rednand and emunand is just one last dummy sector that rednand makes, to extract the rednand and make it a normal emunand, use the hex workshop to open the physical drive of ur SD! and save the sectors (from>2 to 1931264) that will get you a normal emunand.

also ive been trying to update with 3DNUS 9.2 cias pack but every time i convert the updated rednand to normal emunand i get brick when booting from rxTools, anyone knows a better way for me to update it???

But my normal emunand from RXTools is 954 MBs and not 942 MB like the one that I got while saving the sectors, does this matter?

Edit: and when I injected the secureinfo_a, it said decrypton failed and it aborted, but then it said injecting was sucessfull...
 
But my normal emunand from RXTools is 954 MBs(i made it out of my 4.5 sysnand backup and not with MT or gateway...) and not 942 MB like the one that I got while saving the sectors, does this matter?
idk, probably, you should ask about it on the rxtools thread. but my rxtools 9.6 emunand dumped with emuNANDTool is 943 MBs, 11 MBs difference with your nand is big so your emunand is probably messedup with garbage data or something coz you probably made it with MT-Card or gateway and then updated it with rxtools?,.
 
idk, probably, you should ask about it on the rxtools thread. but my rxtools 9.6 emunand dumped with emuNANDTool is 943 MBs, 11 MBs difference with your nand is big so your emunand is probably messedup with garbage data or something coz you probably made it with MT-Card or gateway and then updated it with rxtools?,.

And also I forgot to mention that I backed up my sysnand and I also got 954 MBs on that too.
 
And also I forgot to mention that I backed up my sysnand and I also got 954 MBs on that too.
found the answer:
There are two different NAND chipsets (different manufacturers), and they are of different sizes.
3DS and 3DSXL/LL
Toshiba NAND:
1931264 sectors
988.807.168 bytes = 943 MB
Samsung NAND:
1953792 sectors
1.000.341.504 bytes = 954 MB

so you will need to save sectors 2 to 1953792...
 

Site & Scene News

Popular threads in this forum