hello all ! needed help with my xbox rgh

[Marius Platzner 6]

hi there, i need help with my xbox rgh , after i updated dashboard 17150 and restarted with new dashboard it worked but when i power off and tried later to power on doesn't boot either xell-reloaded or normal , the red light and green comes on and also the green dot on but still doesn't circle for booting up ((

[Swizzy 2083]

What model of console do you have?

[Marius Platzner 6]

xbox 360 slim

[gavin_darkglider 1562]

xbox 360 slim

When he was asking for a model, I dont think he meant slim. Is it trinity, carona v1/v2/v3/v4/v5/v6, or a winchester? These are the possible models for Xbox 360 slim, so I am sure you can see how your answer was not helpful at all. 

[Marius Platzner 6]

well  ... i'm sorry  .. when i saved the current dashboard and load in xebuild showed up corona rgh 2 i have the logs

[gavin_darkglider 1562]

How big is the image? Just trying to figure out if it is a 4gb console.

[Marius Platzner 6]

it has internal hdd 250gb

[gavin_darkglider 1562]

I only ask, because the 4gb nands have a problem where they just stop working. At this point it doesnt sound like a nand issue, but to be sure, any chance you have the retail nand? if so, try removing power from the glitch chip, and writing that back to make sure the console itself isnt broken. Also at this point pictures of the install would be helpful

[Marius Platzner 6]

i have the retail nand and the install log when i flashed but this part of removing power from glitch chip and how i write back the retail nand ?

[gavin_darkglider 1562]

If it doesnt boot, the only way to flash is with a hardware flasher. and removing power is as simple as desoldering 3v3, or 5v from the chip, depending on what chip you are using.

[Marius Platzner 6]

hm i just took of the internal hdd and it boot in xell , how i proceed in this case ?

[gavin_darkglider 1562]

That is interesting, does it boot the dashboard also?

[Marius Platzner 6]

yes amazing , i put hdd back and magically boot in dashboard . thanks for support , :thumbup: :thumbup:

[gavin_darkglider 1562]

glad you got it working.

[Marius Platzner 6]

hm this is fantastic , after it boot up in to dashboard i formated internal hdd and power off then again doesn't boot up either with hdd removed or plugged , this in insane...

[gavin_darkglider 1562]

sounds like a faulty install to me, or a clone cool runner. Can we get some pictures?

[Marius Platzner 6]

now worked again, before i update i had 16202 and never did this before , after update on 17150 like got insane , what pictures are you refering ?

[gavin_darkglider 1562]

Pictures of the install, coolrunner, etc. You could also try building a glitch2m image, which might help.

[Swizzy 2083]

What did you use to flash your console? i'd recommend writing it once again using Simple 360 NAND Flasher 1.4b, it sounds to me like a possible write error or a possible badblock in the making

Basically, when the console alternate between green and red it's because of a MFG error, bad Keyvault or a E5x error

However, as it's a slim it could be soooo many more errors as the ring itself don't alternate, it's just the middle dot... unless of course someone modified your ROL to behave that way...

[Marius Platzner 6]

xeBuild GUI Build Log:

==================================

 Swizzy's xeBuild GUI version 2.095

 Log Started: Sunday 2/15/2015 12:51:40 AM

==================================

 *** Some console information ***

CB Version: 13121

Serial number: 264206123943

Console region: PAL/Europe (0x02FE)

DVDKey:

Console ID: 0972F58108

MFR-Date: 28-09-12

OSIG String: PLDS    DG-16D5S        1532

FCRT.bin Required: False

Using xell-reloaded for Glitch hack

Including dashlaunch... Done!

Including custom dashlaunch settings (launch.ini)... Done!

Copying nand to data directory, this may take a while... Done!

Checking if SMC is Glitch or Retail...

Dumping current SMC... Done!

Checking SMC...

SMC is Glitch patched! it will be used the way it is...

Disabling FCRT.bin check...

Parameters sent to xeBuild:

-noenter -t glitch2 -c corona -d data -f 17150 -b DD88AD0C9ED669E7B56794FB68563EFA -p *key* -a nofcrt  output.bin

Building nand using xeBuild (this may take a while):

---------------------------------------------------------------

     xeBuild v1.14.693

---------------------------------------------------------------

base path changed to C:\Users\Neamtu\Downloads\xeBuild_GUI_2.095\files

---- { Image Build Mode } ----

building glitch2 image

---------------------------------------------------------------

output.bin image built, info:

---------------------------------------------------------------

Kernel    : 2.0.17150.0

Console   : Corona

NAND size : 16MiB

Build     : Glitch (v2)

Xell      : power on console with console eject button

Serial    :

ConsoleId :

MoboSerial:

Mfg Date  : 09/28/2012

CPU Key   :

1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA

DVD Key   :

CF LDV    : 2

KV type   : type2 (hashed - unchecked, master key not available)

---------------------------------------------------------------

    xeBuild Finished. Have a nice day.

---------------------------------------------------------------

Moving output to your destination directory... Done!

Cleaning data and temporary directories... Done!

       ****** The app has now finished! ******

[Marius Platzner 6]

SFCX: Bad block found at 000001DF

block 0x1df seems bad, status 0x00000250

 

i saw this when was backup and flashing , so that could be the problem ?

[Dr.Gonzo 392]

This is quite likely the reason for your problem. You must move the bad block with the well known tools.

[Marius Platzner 6]

how i do that and what is the meaning moving the bad block ?

[Dr.Gonzo 392]

You have a corrupted Storage Cell in your Nand. A Bad Block mover marked this corrupted Cell as corrupted, so that in the future, no Data will stored in these Cell again. It is used another instead. There are sundry programms, that matching Bad Blocks automatically (if its possible).

BadBlockbuster_RC1.rar

[gavin_darkglider 1562]

j-runner automatically remaps bad blocks. you might have to dump the nand with a hardware flasher for that to find them though.(could be wrong about that.)