he doesnt put out detailed info on how he does it for a very good reason

to stop m$ from detecting his CFW, so that the rest of us can enjoy it for as long as possible before they either figure out how to detect it or add a new layer of security in.

quit bitching about how he's not educating you in how he does it, i for one am glad he keeps it private and hope it stays that way.

what possible benefit would it have to publish all this information?

so that there is more than one individual/team putting out CFW faster, so you dont have to wait to play your warez?

scene doesnt prosper? wtf dude pull your head out of your ass!!

in your statement "scene doesnt propser = you having to wait on CFW release" (poor pet)

we have had CFW for over 5 years now, and c4eva has managed to circumvent every single method of disc protection threw at him so far.

wanna learn how he does it?

copy him and learn from the information contained within this very forum.

is c4eva the only one who knows how to do it?

NO hes the only one who is willing to release it. thespecialist was the first to figure out CFW, but he wouldnt release it.

and for making you look foolish, youve done that to yourself by asking foolish questions.

this is x-hacker not x-scene, the hackers dont chin wag here like wives over a garden fence.

installing a new laser is a very simple task

yes there is an anti solder ball that you must remove before installing, but you have to remove it cleanly or you may damage the ribbon cable.

a cheap soldering iron is easily bought to do this, you only need a standard 15W one

correct phonsey, a retail image doesnt patch out the LDV check, and if your CPU LDV is different from the image one it will fail to boot.

you might be able to patch the LDV values in the retail one to match the LDV of your console as it stands, i have never tried that.

whatever

buy a VIA 6421 PCI add on card which will give you two sata ports

use a PC with spare sata port, you are making it harder by using a laptop

copy the file libusb0.dll to the main JF dir from the subfolder libusb to allow JF to load

simple solution to a simple problem and if you cant figure that out on your own, good luck with your RGH youll need it!!

forget trying to undo anything and follow my advice

anything else is wasting your time.

this is easily fixed!! it doesnt matter that the KV is to be remapped, as long as it is done correctly it shouldnt affect the console.

whoever flashed the consoles NAND has obviously not remapped them correctly. i had a jtag stuck on RROD 0022 for months that i could not figure out, had several threads about it on various sites including here, took me ages to figure it out and it was purely down to bad blocks being mismanaged by autoflashing apps.

here what you need to do:

obtain a donor NAND from the exact same motherboard revision, with NO blocks remapped (ie all blocks in correct numerical order) signed with the donor systems CPU key (not yours) (PS i can send you one pm me for link)

then use nandpro in CMD line to remap each block of the donor nand to match the report of your original NAND. this could be compiled into a batch file quite easily to make it faster to do.

start with the first block (1) and remap it to 0x3FF

command for nandpro:

nandpro donorfile.bin: -r16 block1.bin 1 1        <-- this reads block 1 out of your donor file (that i have called donorfile.bin) to a new bin file called block1.bin

nandpro donorfile.bin: -w16 block1.bin 3FF 1    <-- this writes block1.bin previously dumped out of your donor file to the free space at the end of the image.

then remap each block after that in sequence to the last available block at the end of the NAND, ie take one away from the last one you wrote to.

eg

Block 1  --> 0x3FF
Block 2  --> 0x3FE
Block 4  --> 0x3FD
Block 6  --> 0x3FC
Block 7  --> 0x3FB
Block D  --> 0x3FA
Block E  --> 0x3F9
Block 10 --> 0x3F8
Block 12 --> 0x3F7
Block 13 --> 0x3F6
Block 14 --> 0x3F5
Block 15 --> 0x3F4
Block 17 --> 0x3F3
Block 19 --> 0x3F2
Block 1A --> 0x3F1
Block 1B --> 0x3F0
Block 1C --> 0x3EF
Block 20 --> 0x3EE
Block 21 --> 0x3ED

until all blocks listed are remapped to the free space at the end of the image.

open your resulting remapped image in latest 360flashtool to verify that the blocks are found correctly, it should list them in order.

then hook up LPT/USB nand reader and write the image directly to the console.

your console should now be resurrected!! your DVD drive will have to be reflashed to match the donor DVD key etc to function correctly or you will get the "please insert into xbox 360 to play" error.

i have found in my experience that a lot of the 360 based nand flashing apps like xell and flash360 DO NOT remap the bad blocks correctly, this caused me great heartache for 7 months until i figured out that remapping them manually and flashing over LPT/USB works 100% every time.

if you feed these auto apps an image that has the blocks already remapped, they end up writing bad info over the rempped blocks, making the image fail.

the auto apps need a clean image with no blocks reampeed, so when the app detects a bad block in the nand it can then successfully move the block intended for the bad sector of the NAND to free space instead of overwriting the correct block in the free space with bad data.

good luck!!

first thing id do is look up the error code......

then measure all the MOFSETS around the CPU to check voltages etc

i got a batch of the matrix glitchers in and they were all duds

apparently there is a large batch of duds floating around at mo.

findsecdata does not remove an AP2.5 flag, only restores the hdd crippling that used to happen upon a ban.

the hdd crippling doesnt even happen now so findsecdata is pretty much obsolete now.

security flags are also stored within other files on the NAND, so changing your secdata will do f*** all squared to remove your flag.

suck it up and wait for your ban.

cool can i grab it off my live hdd and use it on my jtag?

edit: found the file i need

thanks for the heads up

updated falcon JTAG to latest freeboot build using XeBuild GUI

boots into the new dash correctly etc plays games and FSD

now avi and wmvhd media that worked flawlessly on all previous kernal versions with optional media update on same hdd1 do not play throwing an error code out.

have the codec files been updated in the new kernal or is it a problem with the image?

no this is the new method of drilling the winbond, that supposedly "senses" the correct bonding wire, giving you an audio feedback when you are on the sweet spot

mario can you please provide more info in ENGLISH as this seems very interesting, and you are getting misunderstood with the language difference.

wrong forum lol no1 will answer that question on this board

cheating on live is a no no here

and dont pm me about it again.

did i not just tell him that, over an hour before this post?

the db is FSD2 can become huge, IMHO its not the best idea to put it on your 4GB intMU, it will fill up very quickly depending on how many games you rip to hdd, as it downloads lots of covers, screenshots etc

modeb is for hitachi drives nothing to do at all with slim liteons

i suggest you read the tutorial several times more to understand what is what, as you seem confused between drive requirements, not dissin you man just sayin read up a bit more

the CKi is the successor of the now discontinued CK3 Pro, basically the same thing a molex to 360 power adaptor

you need x360USB to communicate, unlock and flash the drive over USB, it removes the compatibility issues with different SATA ports.

you need to identify the chipset vendor and see if its winbond or MXIC, then you can plan your drive unlock method, drilling the chip for winbond or sputnik hack for MXIC

good luck!

this page speaks of kaid which is a part of a custom FW for many different types of router, i believe there is a good list on that site.

http://www.dd-wrt.com/wiki/index.php?title=DD-WRT_Docu_%28EN%29