Crazy Corona v6 (corrupted emmc?)

[royale.am 1]

Hi guys i'm a new user from Italy, so i'm sorry for my english and I hope you can understand...

 

I have a crazy corona v6 with sk hynix emmc...a customer brought me it telling that after a wrong update (360 already had rgh) it didn't boot more (but i think he has bought it as a damaged console), he doesn't have the original backup of the nand.

 

At first I wrote Xell and tried to boot the 360 to grab the cpukey without success, then i discovered that even the glitchip was faulty so i replaced it with an Ace v2 and then xell booted. So I rebuilded a freeboot image with the extracted cpukey and then flashed it to the console. 360 booted fine into NXE, then I decided to apply offline avatar/kinect update and now problems came...at first 360 was extracting the update but then, after the reboot, only black screen.

 

So i tried to flash again the freeboot but this time in Jrunner and Autogg emmc is detected as removable and there is no more mb dimensions, however i was able to write the image successfully. Then I start the 360 and initial configuration starts (language selection, etc...), but after the configuration only black screen, if I try to boot again, after 360 logo, another time black screen. If i flash the freboot I'm able to do initial configuration every time but then only black screen. Sometimes after flash Xell works, other times 360 didn't even boot if i press eject.

 

I have also checked resistors near the emmc and on the bottom (near r1r1) but they are all ok...the only thing I can imagine is that emmc is corrupted. 

If someone have had similar problems or an idea would be great, this evening I will also post some pictures...

[Swizzy 2084]

It's definitely a bad eMMC chip or a bad write (most likely the former)

I would recommend getting it converted to a 16MB Corona instead, it's fairly easy (all you need is a 16MB nand IC, some resistors/caps to replace the configuration and selecting Corona instead of Corona4G for xeBuild)

[royale.am 1]

It's definitely a bad eMMC chip or a bad write (most likely the former)

I would recommend getting it converted to a 16MB Corona instead, it's fairly easy (all you need is a 16MB nand IC, some resistors/caps to replace the configuration and selecting Corona instead of Corona4G for xeBuild)

Thank you Swizzy, I thought the same...but the customer doesn't want to spend too much so I think I will make him an offer to buy this damaged xbox and then I will try to convert it to a 16 mb.

If you want you can close the post or you can wait this week and then i will post results

[Swizzy 2084]

If you want you can close the post

We don't usually close threads here, as someone else might have a similar problem and want to ask something further, or someone else might have a suggestion that may help...

Personally, i find 4G coronas to be a pain as they're quite often causing weird issues which are hard to fix such as this one or simply that the eMMC ends up being read-only (a very common problem it seems)

[royale.am 1]

Yes, it's also strange that if i try to read the emmc dumps are fine, and since after writing freeboot the initial configuration starts I think also there aren't problem in writing it...I really don't know what the problem could be except for a damaged emmc, I will try to convert it to a corona 16mb and will update you

[Swizzy 2084]

Yes, it's also strange that if i try to read the emmc dumps are fine, and since after writing freeboot the initial configuration starts I think also there aren't problem in writing it...I really don't know what the problem could be except for a damaged emmc, I will try to convert it to a corona 16mb and will update you

Well, it's possible there is a write error too, but it's highly unlikely as you're able to read back and get the same data, i assume this is after a power cycle? (unplug and plug the power cable back in to verify that it's not something cached that's read back, DO NOT turn on the 360)

[royale.am 1]

last update:

 

After converting the corona 4gb to 16mb one, I had flash config 0x00000000...tried nand reset (i/o short), double checked every swapped component but always same flash config...then I checked R2C10, no value on tester, just as opened pads; after shorting it I was able to flash the nand, now everything is working like a charm.

 

I don't think I had the first eMMC problem because of R2C10 and now I don't want to come back to eMMC only to check this maybe someone could tell more about this.

 

Thank you Swizzy for your help, hope someone will find this post useful to solve his problem.