ultimate fix would be to have all BGA redone for GPU and RAM with leaded solder balls then watercool the system.

been said 10000 times if a system is on the verge of RROD, taking it apart and flexing the mobo is enough to break the contacts under the GPU and cause RROD. even 5taking the case off can make it happen. ive experienced it at least 10 times.

the fact that it is an original 20gb system with samsung doesnt help either, those consoles are destined to RROD eventually.

FYI the clamps are not overheating, the GPU is. the clamps simply hold the heatsinks on. its plainly obvious from this statement you havent a clue what you are doing.

you need to send the system to a pro to reflow or reball the system, you have no chance of fixing this properly with your very basic knowledge of xbox 360's.

please dont be offended by this, but its very easy to break the console and quite difficult to fix it properly.

simply replacing the thermal paste and fixing the heatsinks with screws will not fix the core issue of broken BGA connections.

and youtube guides are useless as well please stop watching them and being fooled into believeing you know what you are attempting. you dont.

also the marks on the radiation shield are from the heatsinks getting too hot and basically melting any dust on it to the shield. it is very common, and a sign of overheating.

bad blocks can and do happen quite often, and they are not the bog ossue everyone makes out.

from what you have posted it looks ok apar from the fact that both blocks are relocated to the same sector, or is that a typo by you?

should be

Note: Bad Block ID 0x0019 [offset 0x00067200]
Note: Bad Block ID 0x01E1 [offset 0x007C0200]

Block ID 0x01E1 found @ 0x3FE [offset 0x01077C00]
Block ID 0x0019 found @ 0x3FF [offset 0x0107BE00]

your nand dumps are obviously corrupted, as your original flash does not work either.

how are you comparing dumps? do they match in winhex or are you using a comparing app line total commander?

what is your CB? have you even checked it?

need more info to help

lmao you have had the input of some of the top members of this site and this is how you react?

all they did was correct your grossly incoherent ramblings of a question into concise facts.

enjoy your ban.

if your console is an older one, you can be sure of the JTAG hack if the kernel on the console is pre 7371 the likelyhood of an unhackable cb are low.

if it is a more recent console, it may have kernel 7371, but have an updated cb that will not allow the JTAG hack to be done.

you can dump a small section of the nand in seconds that will tell you the cb before you do any wiring, not sure off the top of my head, but i have seen it done in several apps like magicflasher and XBRflash by my bro Plexo.

this forum should be more for the technically minded people who create all the great hacks we novices use, so dont be offended if some of them flame you for asking what you see as simple things, you must understand that these fundamental things should really be known before someone speaks on this forum.

xbox-scene is a more noob friendly forum you may wish to visit, where you wont get flamed for asking a simple question that could be answered with a google search.

if you are prepared to wait, probably not.

kinda dumb to do all the hard work first then check the cb last...

kids who do that type of $#!t need to learn about pussy.

what arakon said was that your NAND flash may have bad blocks that have not been remapped correctly, that could allow the system to boot, but have odd behaviour.

try reflashing your NAND if you have a copy of the freeboot image that was flashed previously.

or build a new flash with your original dump and flash it using flash360 to remap any bad blocks.

create a bootable usb drive

download and copy over dosflash16

then using a via chipset boot into native dos and perform the 10 sec trick to unbrick the sammy and flash LT fw to it.

the layerbreak should be set in the settings of imgburn to 1913760 to avoid it not being in a .dvd file

and no the ss is required, live or no live, game will not boot with invalid ss

once again, rip your game then run it through abgx360 1.0.5 to fix it.

if you cant back up normal games you are stuffed when it comes to ap2.5 titles.

you can buy a knockoff of the drive caddy on ebay for a small amount

have you set the layerbreak correctly?

and if the ss didnt rip correctly it wont boot either

your reader could be on its way out...

also i made a kreon into an external caddy for a friend, and it simply would not work until i swapped the dvd drive out with his internal writer then they both worked tickety boo.

i know you have a laptop and can't do that, but it may be the problem, just a guess.

would be nice to let us know so that anyone who has a similar problem but is too afraid to ask, can get a solution.

we all are noobs at one stage, and 95% of learning is by f***ing it up and putting it right.

something is wrong it shouldn't take 3 hours to dump a 16mb nand, should take ~ 35 mins.

heres a tip, dump that specific sector on its own with the command

nandpro lpt: -r16 3DE.bin 3DE 1

dump it 10 times, then compare them with total commander, when you find several that match, paste it into your dump with this command

nandpro image.bin: -w16 3DE.bin 3DE 1

then flash this to your console

but TBH if your dumps take that long, you need to look at your setup.

problems dumping = problems writing

you may end up with a corrupted flash and odd behaviour on boot, or no boot at all.

its a bit unfair to say that those apps do not manage bad blocks at all, they didnt for you in that particular console.

I have flashed tons of NAND's using flash360 without one single problem with bad blocks.

moving blocks with nandpro is childs play also!! how hard is it to type a few commands??

have you tried using dosflash16 in native dos mode?

wont work if you have a winbond flash, you need JF for that, but the majority of drives i have done have not been the winbond and can be done much easier in dosflash16

what size nand is it?

a 16mb nand will dump in 35 mins

if you have a bb (256/512mb) nand then it can take much much longer, do the math!

is your cable grounded correctly and shielded?

the dvdrom in an xbox 1 has an IDE port for data and custom power cable that is similar but not the same as 360 slightly bigger.

and yes people have dumped the nand and found that secdata.bin is changed when console is powered without dvdrom.

stop giving out $#!t information, if you dont know then dont say.

as everyone else has stated, buy a teamx ck3 etc or else a RROD xbox for pennies and use that.

all i do is run the .xex file in the latest dashlaunch release on xbins, and it asks on the first line do you wish to set settings

if you say yes it basically asks you all the settings in the ini file and builds the launch.ini for you

if you say no it copies the launch.ini that is present in the dir of the app.