rawnand.bin = 31,268,536,320 bytes
I dumped BOOT and an extra copy of SYS as well, but i haven't been trying to access those via HacDiskMount
rawnand.bin = 31,268,536,320 bytes
I dumped BOOT and an extra copy of SYS as well, but i haven't been trying to access those via HacDiskMount
I explained it in another thread, but well..
It forces the battery charger to disconnect the main battery supply pin (BATFET) from the system.
It's not actually virtual or software disconnect as we call it. It's a hardware disconnect caused by software.
This forces the fuel gauge to reset and also the
Basically it thinks that a new battery was inserted.
Last edited by CTCaer,
Thanks for posting your HacTool results. That's interesting. It could legitimately be a problem with my switch. I'm not sure what a good partition table should look like.
If it is a problem, this is a fun problem, at least, and it's not effecting my switch horizon OS at all.
As for what I've run, only two payloads: the CTCaer/Hekate 2.3 payload through RCM + tegraRCMSmash.
and the biskeydump payload through RCM + tegraRCMSmash
No kips, hbmenus, or modules.
I'm just playing around getting a good NAND backup and getting familiar with things so I can start to contribute.
hex editor shows all 00 at that decimal offset of rawnand.bin
Attachments
Yeah, you are missing the secondary (backup) partition table. That's strange.
Just to make sure I'll make a payload to test.
Likely, David. It is. Those are the INFO messages I want.
Try the attached payload. Run the first option and tell me what you see.
It should be OK.
Thanks for this. I'm seeing the partition from the payload.
I'm starting to think my 256 GB card might not be writing properly.
Attachments
And this is with the latest commits from my repo, correct?
If yes, your card is legit? Have you tried H2testw on it (all available space)?
- Joined
- Jun 24, 2007
- Messages
- 12,007
- Trophies
- 3
- Location
- In the Murderbox!
- Website
- www.twitch.tv
- XP
- 16,143
- Country
Same here. I did it once with a FAT32 microSD and later with a exFAT formatted card. The backup seemed to a bit quicker with the latter, but that's just my feeling.
At work and will run H2testw on the card when I get home.
I compiled your latest commits last night (had to comment out a ment_options sections to get it to compile) and running it without any ini file / configuration options.
I formatted my SD card last night before I went to bed. I will try a fresh NAND dump and see what happens when I get home.
Last edited by 1LastRide,
I used Horizon 5.1.0 to format the SD card again.
I ran the latest version of IPL that I compiled last night to dump boot and full nand. Took just short of an hour to do the dump.
Validation failed immediately.
The file size for Backup/rawnand.bin written is still right.
Perhaps it's extended writing to the SD card that's causing an issue, and it's just writing 00's.
I downloaded h2testw 1.4 from heise.de and am currently running a full write/verify of the 256GB SD card. This is going to take about 7 hours.
I'm bottlenecked by an old USB 1.0 miniSD adapter at about 10 MByte/s
With a fresh Windows exFat format of the SD Card at 256kb allocation (same as Horizon formats, I believe), H2testw is still saying it can only write/verify 255934/299936 Mbytes.
So I wonder if there's a 2MByte partition table for exFat.
Anyway, If the SD card comes back good, my next step is to do a Horizon system reset, format the SD card in horizon, and then try to dump the nand again.
*EDIT* the SD Card test did NOT come back good. It's most likely a 32 GB card sold to me as a 256 GB Sandisk SDXC. Frustrating, but I think I can solve that problem outside here and try again later. The SD Card had a nintendo album and some game updates living on it, so most likely could not fit the nand backup in the memory that was good, which I'm guessing is why all the secondary partition was read from the SD card file as all 00's. Oh, the irony of trying to hack my console with a hacked SD card.
I ran the latest version of IPL that I compiled last night to dump boot and full nand. Took just short of an hour to do the dump.
Validation failed immediately.
The file size for Backup/rawnand.bin written is still right.
Perhaps it's extended writing to the SD card that's causing an issue, and it's just writing 00's.
I downloaded h2testw 1.4 from heise.de and am currently running a full write/verify of the 256GB SD card. This is going to take about 7 hours.
I'm bottlenecked by an old USB 1.0 miniSD adapter at about 10 MByte/s
With a fresh Windows exFat format of the SD Card at 256kb allocation (same as Horizon formats, I believe), H2testw is still saying it can only write/verify 255934/299936 Mbytes.
So I wonder if there's a 2MByte partition table for exFat.
Anyway, If the SD card comes back good, my next step is to do a Horizon system reset, format the SD card in horizon, and then try to dump the nand again.
*EDIT* the SD Card test did NOT come back good. It's most likely a 32 GB card sold to me as a 256 GB Sandisk SDXC. Frustrating, but I think I can solve that problem outside here and try again later. The SD Card had a nintendo album and some game updates living on it, so most likely could not fit the nand backup in the memory that was good, which I'm guessing is why all the secondary partition was read from the SD card file as all 00's. Oh, the irony of trying to hack my console with a hacked SD card.
Attachments
Last edited by 1LastRide,
hi
so if i don't have much space what is the most important backup i should do (Dump eMMC BOOT+Dump eMMC SYS) enough to be able to restore my system if something happen
thanks
so if i don't have much space what is the most important backup i should do (Dump eMMC BOOT+Dump eMMC SYS) enough to be able to restore my system if something happen
thanks
That's unfortunate :/
I hope that you can return it and get your money back. Send me a screenshot of Print sdcard info and maybe I can tell you if they also faked the vendor details.
And yes, a fake sd card that can reply for addresses out of its real max, it normally replies with 00s or it starts sending the data from the start.
Do BOOT0/1 and raw first. And then do a SYS one.
Similar threads
- No one is chatting at the moment.
-
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
