3 red lights after xell install

[TAR]

Hi guys, i got a falcon here. Connected nandx and dumped nand 4 times. Got 250 error reading block 357. Ive read somewhere to ignor this as its probably a 0 or something like that. Anyway , wrote xell and hit eject , all i get r 3 red lights, and no picture. If i flash back the original nand, boot, i still get the 3 red lights. Now if i unsolder one of the jtag wires it boots fine ( original nand ). So ive manually injected my rawkv, rawconfig into the lateset xbr, flashed that but still i get the same. Checked my solder looks fine. Any ideas, is there something ive missed?

 

[manwithoutname]

When you flashed back the original NAND, did you disconnect the power supply for few seconds and tried again?

You are using the traditional non xenon JTAG method or the alternative SMC points?

 

[TAR]

hi m8, thanx for reply. Im usung the alternate point underneath mobo(pic attached) if i reflash the original nand, it only boots if i disconect the yellow wire ( that goes to thr rol board ).I take it this is corrct?

btw im using the diodes from the nandx kit.

 

[manwithoutname]

I'm not sure if that's the right point for the alternative to DB1F1, but I bet your console is shortening when it refuses to boot with the JTAG wires all connected.

When you get RROD with the original NAND, get a secondary code.

Also you might want to try the alternative SMC points using AUDIO_CLAMP & OPEN_TRAY signal connections, use Azeem's tutorial from here http://www.team-xecuter.com/forums/showthread.php?t=55189

I used it my self on a Falcon board day before yesterday and used my short method for xell and freeboot with a little remapping from nandpro and it worked.

 

[TAR]

k thanx, altered the wiring to that tut, and it boots the original nand no probs. now to do the image. Ill report back in a bit. Thanx m8.

 

[manwithoutname]

Trust me, once you done it this time you'll use it all the time. I do this as standard now with all HDMI consoles.

Remember there is no need to install XBR, just get the falcon.bin file from xbins folder within JTAG tools. Extract it's SMC file, alter the points and then place it back in JTAG Tool xbins and flash it. You might notice that the original xell file will be 1.4mb and after modification is 16mb. That is normal, just flash the whole 16mb.

Next remember to extract the SMC file again from the modified xell image file and place that in the SMC folder within JTAG tools before compiling your freeboot image.

If you have any bad blocks you'll need to remap freeboot image after compiling as for xell it's not necessary but it's hit or miss so I always remap them anyway.

 

[TAR]

Update.... n1 m8 worked first time. but if i boot with eject button, it boots to the dash. How do i get my cpu key etc. btw i does work cause i can run xexmenu.


edit..... just read ur post m8, so i need to do this to xell. flash my xbox and read it that way?


Another edit....to answer my question YES! xell booted 1st time..wow that was easy lol. Again thanx m8 u a star.

 

[M AzeeM K]

Update.... n1 m8 worked first time. but if i boot with eject button, it boots to the dash. How do i get my cpu key etc. btw i does work cause i can run xexmenu.


edit..... just read ur post m8, so i need to do this to xell. flash my xbox and read it that way?

Remember to try different settings on the JTAG QSB, preferably without the resistor. Before a month ago, there was an Xbox360 which won't boot XeLL and would only boot to XBR. But after sometime, I found out that if the JTAG QSB switch was set on to use the 330/470 resistor, XeLL won't boot. But if it was set on not to use the resistor, it would boot XeLL with the eject button.

 

[TAR]

Im not using the qsb's m8, just the direct wires. Got xell working and got my cpu key. Trying to get freeboot on now. Ive made a freeboot image with my cpu key, edited it using update my smc and flashed it. On powering on the green light in the middle just flashed and nothing else. so that didnt work......

 

[M AzeeM K]

Im not using the qsb's m8, just the direct wires. Got xell working and got my cpu key. Trying to get freeboot on now. Ive made a freeboot image with my cpu key, edited it using update my smc and flashed it. On powering on the green light in the middle just flashed and nothing else. so that didnt work......

You're doing it wrong. What you have to do is to extract the SMC out of the working XeLL image and put that SMC file(falcon.bin) in the "SMC" folder within the Jtag Tool folder. Then make a freeboot image using Jtag Tool and flash it straight to the console. No need for UpdateMySMC.

 

[TAR]

k, ive got a working 16k xell image. if i run dump_smc form xell image, it goes thru the motions (very quickly ) but nothing is saved in that folder ( where dump_smc-from xell is located ). If i use dump_from any image, the image is save but only 12 k. if i try to make a freeboot image the prog says image wrong size . i know im doing somthing wrong but what? lol

edit... tried making a freeboot image from XBR_smc but that gives a e79 error..

 

[M AzeeM K]

k, ive got a working 16k xell image. if i run dump_smc form xell image, it goes thru the motions (very quickly ) but nothing is saved in that folder ( where dump_smc-from xell is located ). If i use dump_from any image, the image is save but only 12 k. if i try to make a freeboot image the prog says image wrong size . i know im doing somthing wrong but what? lol

12KB is the right size.

 

[TAR]

Thanx for the files....K, using jtag tool, ive updated the smc folder and the xell folder with the already modified files. made a freeboot image using my original nand dump, but i still get just a green flashing light ( middle 1 ) and nothing on the screen. Would this happen if ive writen down the cup key incorectly?

 

[M AzeeM K]

Thanx for the files....K, using jtag tool, ive updated the smc folder and the xell folder with the already modified files. made a freeboot image using my original nand dump, but i still get just a green flashing light ( middle 1 ) and nothing on the screen. Would this happen if ive writen down the cup key incorectly?

It means there is something wrong with the SMC file.

OK. Leave this. Send me your Original NAND dump & CPU Key and I will make a freeboot image for you. See if it works for you.

Or, you still have that working XBR image, right? Dump the SMC out of it, and copy it over to the SMC folder in Jtag Tool. Then make a freeboot image and see if it works for you.

 

[TAR]

k its dawned on me, why this aint working, im a tit and u will laugh when itell u. the original dash was 6717. freeboot needs a das of 7xxxx. correct me if im wrong. so now ive re flashed original nand, updated to dash 7xxxx. now im going throught the whole process again lol, wish me luck!

 

[BGAMods]

lol, i did this last week. was having loads of trouble with e79 then realised my dash was the same as yours. so updated to 7371 and bang worked first time. hope it works for you mate.

 

[M AzeeM K]

k its dawned on me, why this aint working, im a tit and u will laugh when itell u. the original dash was 6717. freeboot needs a das of 7xxxx. correct me if im wrong. so now ive re flashed original nand, updated to dash 7xxxx. now im going throught the whole process again lol, wish me luck!

Yeah, you should do that. How come you missed it since its like the first thing that is mentioned in the tutorial?

 

[TAR]

soz m8, i always read the manual when it dont work

 

[manwithoutname]

Sorry I was out and just got in so couldn't follow this. I'm assuming you verified the CPU key in 360 flashing tools? Cause if the CPU is incorrect it will display similar behavior (I can count the number of times I mixed the c's & e's) on xell screen .

Also was there any bad blocks from your original dump?

Update us please !!!

 

[TAR]

yes m8, original nand dump had 1 error.....250 error reading block 357..

ive checked the cpu key and extracted the kv etc. checked the kv all looks good.... help