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.
I did the donor n4nd with those files he is teaching how to do that but with the mb I tried didn´t even turn on so that step is wrong the correct way is by decrypiting the original n4nd and with that create the correct donor n4nd like he says at 42:27 so why did he show that wrong step or at least not working for any 360 mb.
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
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
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
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.
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.
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
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
Why do i have to make so many donors, dont i just need the xell donor and then unlock my original dump with the cpu key and then just create a xebuild image with your original nand why make another donor after that ? and will that donor become your new original nand ?
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.
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.
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
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...
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?
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.
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.
I bought three for 115 Canadian(about 80 American). A Microsoft refurbished Zephyr, a late Jasper or early Tonasket and a Corona Slim. Four controllers, two OEM and two brand-new Afterglows. Knowing about the nand on the slim makes me want to keep it shelved for a while, unless I feel like trying it with the kinect.
![[Bad] - YouTube ВСЁ? (победа VK и прощание с подписчиками)](http://i.ytimg.com/vi/pQ1bCOW5270/mqdefault.jpg)
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.
He mentions this at 42:27
I did the donor n4nd with those files he is teaching how to do that but with the mb I tried didn´t even turn on so that step is wrong the correct way is by decrypiting the original n4nd and with that create the correct donor n4nd like he says at 42:27 so why did he show that wrong step or at least not working for any 360 mb.
Holy shit thank you for this!!!! I've been waiting for a proper tutorial on how to do this. Thanks so much!!
I have been having this issue with a thrifted Xbox 360 E , thanks for the video Modzville!
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
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
Ill save this video i wanna learn to do the donor build of xell
Fantastic work. Hopefully someone can make a pain free solution in the near future. 😊
Many thanks for this, managed to save an E model with a dying emmc.
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
There should be more components, no?
@@morderus0033 Not needed.. and do not remove anything not mentioned here
Love the r2d2 resistor.
The hire ups at Microsoft must be straight up Star Wars nerds.
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.
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.
Nice job man you’re amazing at soldering
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
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
Why do i have to make so many donors, dont i just need the xell donor and then unlock my original dump with the cpu key and then just create a xebuild image with your original nand why make another donor after that ? and will that donor become your new original nand ?
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.
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.
I think you can extract the dvd key from the dump as well
Hey Modzville ! is there a possibility to upgrade the Cpu or Gpu of a Dreamcast like the Ram Upgrade (16MB to 32MB) ???
Yes, for the original GPU and CPU the console was designed for.
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
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 have some unlocked pcbs, I just use those for slims.
@@ModzvilleUSA Unlocked PCBs definitely makes it easier, no need to risk damaging your drive or spend wads amount of cash on expensive hardware.
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.
if the console green light not boot up meaning what?????
Soooooo can I get a 64gb chip and keep the supporting components?
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?
what the size all SMD resistor & capacitor?? 0402 or 0603??
Wait, so, dude is changing his 4GB built-in storage 360 to be a no internal storage type 360? 😢
Este procedimiento es solo para que quede con rgh?
Can i use the donor nand to fix my Corona disk drive ?
Wii Us are also dying from faulty flash storage, Voultar had made a great board to repair bricked Wii Us.
One day, if I get another gamepad, then I'll be sure to fix up my Wii U a bit.
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.
Trinity consoles only had 16 MB NANDs. The 4 GB module has nothing to do with the NAND on a Trinity console as far as I know
I'm talking about desoldering the TSOP on the 4GB modules and using as a replacement for the corona.@@Harmonic14
Great works.... you did it 👏
a lot of thanks it works for me ! thanksss
Great vid Mods!!!
Did this yesterday, thanks.
Funny this shows up the day that I have to resolder the PLL wire on my Trinity RGH 1.2, I'm assuming they fall victim to this too eventually.
This applies only to 4GB Corona motherboards with eMMC.
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.
Didn't have a post fix so tried a cut up dat0 adapter...worked a few times but very unreliable. Waiting on postfix from Ali...lol
Great work
Cool, but for $20 it's just easier to buy another 360. Spend $100 and buy five.
I bought three for 115 Canadian(about 80 American). A Microsoft refurbished Zephyr, a late Jasper or early Tonasket and a Corona Slim. Four controllers, two OEM and two brand-new Afterglows. Knowing about the nand on the slim makes me want to keep it shelved for a while, unless I feel like trying it with the kinect.
Sometimes is just about the project and not always about what’s cheaper.
What if you wanted to use a new nand chip
Using a new nand is totally fine
My WiiU's internal storage also just up and died even though the thing only had like max 400 play hours in.
Voultar has made some Wii U NAND recovery boards.
that intro is hysterical
Programs with finish-tunes are so annoying.. that brings me back to many keygens or no-cdcracks back in the day :D