[4DoorITR]

Following instructions months ago I made a NAND dump using Preloader before converting to DEX. Long story short I bricked attempting to get back to CEX. The Preloader dump errors in flowrebuilder and doesn't look valid when viewing a hex editor. Anyone know how this backup can be used if it can be at all?

The bootloader is hidden somewhere else in the dump.

[tjhooker73]

Originally Posted by 4DoorITR Following instructions months ago I made a NAND dump using Preloader before converting to DEX. Long story short I bricked attempting to get back to CEX. The Preloader dump errors in flowrebuilder and doesn't look valid when viewing a hex editor. Anyone know how this backup can be used if it can be at all? The bootloader is hidden somewhere else in the dump.

You should have made and checked your dump :/

[4DoorITR]

I have already made a valid dump with Progskeet. I am just curious as to where the bootloader is located in a preloader dump. I remember reading on the wiki that HV masks or relocates the booloader(s) to a different address. Unfortunately it is down at the moment.

[haz367]

there is a way to "add" that missing first or second whatever.. "bootloader" back into the software nand dump, excactly how? its around 17MB less? so a block of 17,825,792 bytes to make it 256 mb hardware valid dump or something..

missing @ 0x000000 in software dump

256MB NAND consoles have a hidden section of size 0x40000 (0x200 * 512 byte sector = 0x40000) hidden by the hv. The hv hides it at address 002786E8

[4DoorITR]

No I'm not saying add it back in. It's there just not in the right place. The filesize is correct, so it's either not in the correct location or filled with 0's or F's.

Thanks for that code that's what I was looking for.

[haz367]

just asking....u say filesize is correct?
its missing some mbs right? vs a "hardware" dump restoring a software NAND dump not working with flasher correct?), if its hidden, its that adress/offset ^
its not at offset 0, second bootloader is in dump, paste write that same block into right place = 256MB hardware dump? i've seen people posting about...adding it back in to make a flasher compatible dump?!

or is it..when changing 0's & F's for other values making the size bigger? i'm stupid so nvm the question..

[4DoorITR]

Yes it's the same size as a hardware dump. I do not know where the bootloaders are if they are in it at all. Jaicrab is known for making crap so who knows what happens. What I am wanting to do is move the bootloaders to the correct offsets so I can use this dump with flowrebuilder in case my other dump fails at fixing my brick.

[haz367]

? no they are not the same size?! 239mb software vs 256mb hardware NAND dump, the first missing that 1 bootloader of 2 in total, and the missing one can be injected to make it 256+2 bootloaders(identical)...something must be correct

[4DoorITR]

Well I'm looking at both the preloader dump and the one I made with the Progskeet and they are the same size down to the last byte. Don't know what else to say.

[JonahUK]

Preloader makes a full 256mb dump.
I used that when I went DEX and used the same dump to go back to CEX with no editing