GENERAL High Fan Speed after NAND Read

[mightyi]

I've been working on a problem corona v2 4GB recently, trashed during a bad CR3 Pro attempted install! managed to repair all the damaged tracks etc, but tried to read the NAND tonight through the 4GB RW kit and had problems with the cable not being detected at all; in any reader. eventually resoldered all the connections to the mainboard and got a clean read and write to/from the NAND. However, during my attempts to read the NAND, the console started booting up with the CPU fan running at the equivalent of about the 65% setting in FSD, and has been doing it ever since. Ive left it running for ages and it never slows down (does it in NXE/FSD and in Xell). Hoewever, if i got into FSD and turn the fan speed up then back down to "Auto" again, the fan then slows down to normal again.

Any suggestions? apart from this weird issue, the console seems to be running perfectly!

 

[Krafter]

Rebuild and reflash your image maybe? Sounds like something didn't compile right.


Sent from my iPhone using Tapatalk

 

[Martin C]

pics of your soldering is needed, obviously.

 

[mightyi]

@Krafter - thanks for that idea! i reflashed the 16202 RGH image again and the speeds were restored. strangely, when i built the new one again the same problem appeared again!

However, after deleting the existing j-runner installation and recreating the image in a new copy, the image worked nicely

One thing i did find an issue though - I thought that it would be worth doing a complete original NAND rewrite when i started having these problems, but after writing about 10-15% of the NAND, j-runner gave me an error "Device not ready", after which the image size of the NAND refreshed and became 0. If i unplug the power supply and reinsert that and the usb card reader back into the machine, the correct size is identified again. Writing a 50mb image works every time, as does reading the full 4GB image...just not writing. Is this an issue within J-Runner?

Another strange thing is the process to get the NAND to be detected and with the right size. I've tried a few usb readers, but the best one strangely is the one in an old vodafone mobile broadband dongle! i've got another straight usb reader but that is painfully slow to read/write. But with any, the only way for me to be able to detect anything is to unplug the power from the xbox, insert the card adapter into the usb reader, insert that into my machine and let it detect; then plug the power cable back into the xbox....this is the only process that works; and it does it every time! Des anyone else find things quirky like this?

 

[Martin C]

"But with any, the only way for me to be able to detect anything is to unplug the power from the xbox, insert the card adapter into the usb reader, insert that into my machine and let it detect; then plug the power cable back into the xbox....this is the only process that works; and it does it every time! Des anyone else find things quirky like this"

This isn't quirky. If you don't do things in the right order then the Phison chip isn't initialised properly. Same thing with a NAND-x - it needs to be connected to a console AFTER you connect the PSU.

 

[mightyi]

@Martin yes i can understand there has to be an initialisation process for things to work, I just expected it to be that the X360 would need power first, before connecting to the USB reader! Was curious if everyone else found that was the way they worked as well