Originally Posted by deank
mM cares for the first 264703 bytes of the NAND dump it creates (EID0 should start at 0x40800 for one sector to 0x409FF). If it finds it there (+the IDPS at 0x40870-0x40890) it will accept the 239MB dump, compare the IDPS with your console and proceed if it matches. You can try to trim the last 6MB and load NANDBIN in mM. It will ask for 4 confirmations before proceeding if the dump/IDPS is valid, so you can abort at any time.
************* [ - Post Merged - ] *************
I would also suggest that people use ProDG for "System Update" via LAN/WiFi when installing firmares in DEX mode (going to 4.** and going back to 3.55DEX downgrader).
If the next update of mM supports supports full NAND will be great. Really looking forward to it!!
1. Does installing (Going up and down) DEX firmware directly hurts the systems? Whats makes using ProDG for "System Update" different?
2. So by using ProDG/TM
, it bypasses "syscon hash checks" during system updates?
3. Does this mean, ALWAYS
when going up and down firmware when you are on DEX
4. Does this also mean, ALWAYS
when you are switching between CEX<-->DEX