thats a pretty big assumption right there, where did you pull that fact from?

dude seriously read up a bit before coming on to the top 360 hacking website and making a complete dick of yourself

seriously!

or eles go back to xbox scene its the ideal place for newbs to ask dumb questions.

to answer one of your dumb ass questions

they are supposed to be the same yes, and if they arent then your setup is giving you bad dumps and you risk killing your xbox if you proceed to overwrite your NAND.

hey its only been said a billion times already, and theres another time!!

if you replace the drive with the exact model of drive and simply spoof key over you should not be in any danger of a ban

this is sure to be a pain in the ass

imagine when you are seconds away from that oh so hard to get achievement youve been trying for hours, hell days to get and then the f***er shuts down!!

jesus man you bump a thread 2 days after the OP told us all it was sorted?

get your head out of your ass!!

nice one terry glad you got it sorted!!

thats exactly what i advised him in my long post above.

you need to remap the blocks in any image that you intend to flash to the xbox, to match the remapped blocks from your original dump.

are you using the correct SMC for your board revision?

checked JTAG wiring?

of course, if you have an exploitable kernal on the xbox (<=7371) you can retrieve the key from the motherboard with XELL

thats your problem right there

why did you remap sectors in your original dump?

your dump when opened in degraded tells you that the blocks are already remapped, and you have then remapped crap over the good info in the remapped areas, corrupting whatever file they were part of, in this case probably part of the bootup animation file or critical boot file.

did you keep another copy of your orig dump before you remapped anything?

if so use that untouched to create a freeboot image which will not have any sectors remapped, then remap the blocks of the freeboot image to match what degraded tells you

eg (where freeboot.bin is your created freeboot image)

nandpro freeboot.bin: -r16 0x14e.bin 0x14e 1
nandpro freeboot.bin: -r16 0x159.bin 0x159 1

nandpro freeboot.bin: -w16 0x14e.bin 0x3FF 1
nandpro freeboot.bin: -w16 0x159.bin 0x3FE 1

nandpro lpt: -w16 freeboot.bin

then reflash this to your nand.

or else play music from the hard drive whilst playing to keep it on

thats great for exploitable consoles, but until an expoit is found for the current kernal there is no other way to play backups, so the topic will continue.

reverse you are as always correctt dude

but ive seen some crazy positions of the warranty stickers on the 360 soid say that they dont do that for this console.

the convo about the stickers is a bit of a silly argument, any sticker stuck on the damn console to see if youve opened it is a warranty sticker, end of argument

can we keep the topic on course about the consoles hardware, and possibilities of hacking the damn thing instead of arguing over a f***ing sticker.

i laughed at the "acid decap was bull$#!t" comment

did you not see the pic?

roffle!

some high res pics of the dvd drive PCB looks good for MRA hack to me...





just need to figure out the points to cut and bridge

2 hrs my ass 2 seconds found this

http://www.xboxhacker.org/index.php?topic=14040.0;topicseen

look a bit harder next time

yes it can be recovered theres a thread in the forums covering what to do when via's are destroyed

look for it

or send it to a pro if you cant do it

reflow the RAM chips on the top side of the mobo with liquid flux will sort it out

come on dude we are not here to wipe your ass for you, rise to the plate man.

ill help you certainly but im not doing it for you, you should learn yourself.

open your orig dump in degraded 1.1 and post a screenshot so i can show you and others reading

it will say

bad block found at (for example) 0x01A
block relocated to 0x3FF

may be lots or just a few

then you need to read out the corresponding sectors from your freeboot image using nandpro name them sequentially

then inject them back into the freeboot image where degraded tells you they should go starting at 0x3FF working backwards (assuming 16mb nand 256,512 have diff adress i cant remember off the top of my head but can be found on the forum boards)

then when done put the freeboot image on root of USB drive named as updflash.bin

load flash360 and choose to flash without keeping current kv and config

job done

if you post a screenshot of degraded i will give you the commands for nanpro

its quite simple to work out really each bad block will be listed sequentially and are remapped in order backwards from the last block.

anyone in the US got their hands on one of these yet?

rip it open and take some pics im dying to see the internals

i cant get one until July 16th

and when i can get the funds lol