Nice job! Heads up, you don't need to use the donor nand wizard. With the 4GB dump loaded, change the type to 16MB, then hit Create and Write XeLL. Then once the 4GB nand decrypts with your CPU key, just change it again to 16MB, then Create XeBuild. Done. Even if you are going to use the donor nand wizard, you did it the really hard way. Instead of using those random donor files which you don't need, you can use the ones from your dump or if you can't, then check the boxes to use the built in donors.
U can do make it simpler by: Components to be Removed on top of the board: - Just the 4GB IC Components to be Removed on bottom of the board: R1R1 = 1K remove R2R2 = 50K remove R1R3 = 50K remove R1R4 = 50K remove R1R5 = 50K remove R1R6 = 50K remove R1R7 = 50K remove R1R8 = 50K remove R1R9 = 50K remove C1T3 = 0.82uf remove C1T5 = 4.7uf remove Components to be installed on top of the board. R1E8 = 10K U1E2 = NAND 16 MB Components to be installed on the bottom of the board. R2R1 = 2.2K R2T2 = 10K R2T14 = 10K R2T15 = 10K R2T16 = 10K R2T7 = 10K R2T8 = 10K R2T9 = 10K R2T13 = 10K
I did an RGH3 on a corona that let me read the nand and write an ECC but it had a few bad blocks in the XELL part of it. It never would boot with the full updflash. Ended up swapping over a nand chip from a junk trinity and using the decrypted dump to make a donor nand. Works like a charm and it even shows up as a corona board and trinity flash in Dashlaunch.
at 6:15 when you explained how you were trying to force it to write xell by repeating it back to back, that could work if you combine spamming that with heating up the emmc chip using a heat gun turned down to low, or a hair drier. some light heat and a generous ammount of flux to reflow the solder (dont melt anything), or if youre scared of soldering with a heat gun like that then try even less heat and just getting the emmc a little bit more warm then ambient temps while youre flashing it. may not work if nand is having internal errors instead of connection issues with the board, but its worth a shot at getting it to respond the easy way
Thank you for the video. Just want to point out, the Resistor book you link is for a book only, no resistors are included. last page says 15 page blank book. and it for sure is a blank book that I got lol.
Hey, that was a bit weird but... here goes. My monitor had an entire row of stuck pixels and watching your vid in fullscreen fixed it. So that's that I guess. Anyway, carry on.
Just worked on a Corona 4gb today. except for me it actually let me write and i’m able to boot up to XELL. The thing is my xflasher doesn’t let me write to the NAND even though my soldering is pretty good. I’m assuming my 4gb emmc is also dying because in the before i started anything, i formatted the storage and it was giving me the same error as you but i didn’t think much of it. Just wanted to ask for your opinion of anything else i can try or if it’s most likely the emmc issue. Thanks
I have an xbox 360 (corona V4) without nand. If I change to a 16mb nand, how do I perform these steps in JR programmer? as it will not be possible to extract the CPU Key
Personally I don’t mess with corona consoles don’t feel like needing a postfix for versions that need it, the 4gb nands go bad, the resistors can go bad and cause the console to “overheat”. I always try and find a trinity as they never have caused me much issues and you can remove the 4gb add on on the motherboard and get a pcb that you can solder to the board and add up to a 2tb usb internally.
my nand Slim S White also corrupt.. whatever im succesly write using JRunner but after boot likes "write protected", nothing change after boot.. im succesful dump Nand, size is 48MB.. if convert to 16MB is fit??
From what I remember you can swap the slim liteon with a phat unlocked drive but if the slim liteon is never going to be used you may aswell do the Kamikaze hack on it nothing to lose...
I wonder why they scratch those marks onto the nand? I notice it on a lot of consoles they are marked with what looks like a scribble of some sort. Maybe just to show at a quick glance the nand has been written to? idk
I followed this with a v2, all of my soldering checks out, it will read and writes, I am using a blank nand TSOP and my console still only beeps, it will not boot into XeLL and not sure why.
I’ve had a dead 4gb module on a Trinity before. When that happens it hangs on the 360 logo. You can simply unplug it and call it a day as Trinity has a 16mb nand as well as a 4gb emmc module
@@ModzvilleUSA Well Trinity motherboards only have 16MB NAND configurations. The 4GB module is just a formatted flash drive using the XTAF format. It's no different than plugging in a flash drive into the console however from that specific location the system treats it as internal storage.
@@TheModShopCOSorry to bother you but I have a question regarding 4GB Coronas. In the storage menu, I was able to move important system files and have them be stored in the USB Flash Drive instead. Has anyone done this before? This option only appeared when I deleted everything on the 4GB Memory Unit and formatted the USB Storage Device as the main System Drive instead. Now "USB Storage Device" has been renamed to "Memory Unit" by the system and the other Memory Unit (4GB) is no longer being used. This also restored functionality back to my Xbox 360 when previously there was symptoms of a failing NAND. Any information about this would be appreciated as I couldn't find much about this specific scenario online, and I would like to know if this is a fix or not. More info: I've been using this Xbox without hassle afterwards for months. Only important system files and updates are allowed to be installed and stored in the USB Flash Drive as that's how the system formatted and intended its use. Game titles and data are stored in a 500GB HDD that I plugged in. The 4GB Memory Unit is completely empty and not being used by the system whatsoever. So far there has been no issues at all and everything is running smoothly.
here's a question. If the 4gb emmc completely fails, will that prevent the console from booting? Or is the purpose of this swapping with a 16mb nand only for RGH'ing?
When the 4gb nand chip (emmc) fails the system will not boot anymore. You can tell its on the way out when you are unable to update the dash, cannot make changes to system that save. Trying to save causes system to freeze up etc..
@@LeapFrog_Radio interesting, so basically fails just like the Wii u. I have a 4gb model that isn't rgh'd yet, so maybe it's time. Interesting, as how when 360s first came out they were failing due to heating up and cooling and that would cause the bga to disconnect. Now we have to worry about failing nands. I know it's not common, and can be fixed, but still. Interesting times for the 360 going forward.
What other symptoms are there of a failing module? My corona randomly started to stutter no matter what game I play. Hardrive, disc, usb, all have slight stutters with no plugins enabled Also had issues when changing plugins, I’d save them in dash launch, reboot, and the plugins would still be there. Happened two times in a row before it actually saved. Wonder if it’s the same issue. As I have no soldering skills I’m probably just gonna have to buy a new rgh. Gonna try to get a jasper or trinity.
I have two bad Corona 4GB's here but not the same memory as in the video. Mine have a very small thin chip at U1E3 and the 4GB NAND is directly underneath on the bottom side of the motherboard. Wondering if the same procedure will work, on top side? Pretty sure the NANDs are also corrupt and write protected. Can I take a donor 16MB NAND from an old Xenon and can I flash it to Corona ECC on the Xenon before removing?
ive been working on a 16mb corona v2 all night trying to figure out why xflasher wont read the nand, any help or thoughts on this would be appreciated, good solder nothing ugly, new flasher and has been used on the last rgh i did so i know it works, but not sure why it wont read the nand using jrunner, drivers are up to date as well. this is what im getting when i hit read nand J-Runner with Extras Session: 09/03/2023 5:06:05 Version: 3.3.0 Status: Up to date xFlasher: Waiting for device to become ready xFlasher: Checking Console... xFlasher: Device Not Initialized xFlasher: Checking Console... xFlasher: Device Not Initialized
How do you know when your 4gb nand is dead? I tried soldering the wires 3 seperate times to my current console and cannot get it to recognize the disk drive. ( i have succesfully done a few 4gbs in the past)
if it beeps instead of turning on it's dead, or if you get it to boot and go to storage and it says unformatted that is a clear indicator that it is failing and or dead.
can you use the nand IC of a 4gb module found on trinity consoles? it seemed to work for me I was able to write to it but now it still only beeps and I am not sure why, everything checks out.
