Flash Controller :/

monkey3200

Full Member
Sep 10, 2010
28
0
Haha it took me a little longer than 20 seconds. The soldering looks good but I couldn't test anything because I couldn't get xbins to run and couldn't find mirrors for xbr.

I'll have to try tomorrow :/


Also a weird issue I'm having, my xbox won't turn on with the ROL. I flashed xell once but I flashed back to stock shortly after. I even updated to 7371 and I'm still getting the issue
 
Probably, you must have by accident bridged two points on the ROL while taking off the Yellow wire. Therefore, the ROL isn't working.
 

monkey3200

Full Member
Sep 10, 2010
28
0
Wow. I've made some progress but I haven't been able to get freeBOOT running.

I was able to change my smc points and run xbr and xell and get my CPU key.

I couldn't use xbr to fb because my console is actually a zephyr.( I found out by putting my NAND in flash dump tool)p I've been using falcon files this whole time. I have the cb of 4750 or 4570 I forgot which. But I know it's exploitable because it used to have the blades dashboard.

Since I couldn't use xbr to fb, I had to make my fb image with jtag tool and changing my smc in the program files.

Upon making it I wrote it to the NAND. I would either get e79 or 0022.

Keep in mind that I did get xell and xbr to boot. So I highly doubt it's my soldering. An I flashed the original NAND back and it booted fine. So it doesn't have a real 00220
 
Wow. I've made some progress but I haven't been able to get freeBOOT running.

I was able to change my smc points and run xbr and xell and get my CPU key.

I couldn't use xbr to fb because my console is actually a zephyr.( I found out by putting my NAND in flash dump tool)p I've been using falcon files this whole time. I have the cb of 4750 or 4570 I forgot which. But I know it's exploitable because it used to have the blades dashboard.

Since I couldn't use xbr to fb, I had to make my fb image with jtag tool and changing my smc in the program files.

Upon making it I wrote it to the NAND. I would either get e79 or 0022.

Keep in mind that I did get xell and xbr to boot. So I highly doubt it's my soldering. An I flashed the original NAND back and it booted fine. So it doesn't have a real 00220
Making a freeBOOT image first, and then changing its SMC won't work. What you have to do is to modify the SMC file first, then use the modified SMC file while making the freeBOOT image. This freeBOOT image should work then without any error.
 

monkey3200

Full Member
Sep 10, 2010
28
0
Yes I know. And that's the tutorial I used, but it says if you can't make your fb image using xbr to fb. Then you can take your alt smc image, put it in jtag tool, enter your CPU key and have it make the fb image there. Bu that didn't work for me
 
Jun 4, 2010
3,080
0
I'm sure it's been said various times on how to make it. Look at my signature, download the pack and extract the files. Place the relative boardname.bin file from the SMC folder into 'C:\Program Files\Jtag Tool\SMC'

**Make sure that Jtag tool isn't running when doing these changes as I found it has the tendency to give error messages or currept some of it's files and then you'll need re-install it to fix the problem.

Next just use your obtained CPU key into JTAG Tool and compile a copy of Freeboot and flash it to your console as normal.

**If you have bad blocks you might need to remap your freeboot image but try it first hand and see what you get.
 
Jun 4, 2010
3,080
0
So lets confirm all these been done:

1. Yellow wire soldered to the AUDIO_CLAMP?
2. Red wire soldered/connected to the dvd OPEN_TRAY signal?
3. You copied the falcon.bin (12kb) file from the pack you downloaded of my link and placed the file into C:\Program Files\Jtag Tool\SMC then compiled freeboot using your original NAND dump?
4. You got no bad blocks or if you have you did remap them in your freeboot image before flashing it to the console?
 

monkey3200

Full Member
Sep 10, 2010
28
0
So lets confirm all these been done:

1. Yellow wire soldered to the AUDIO_CLAMP?
2. Red wire soldered/connected to the dvd OPEN_TRAY signal?
3. You copied the falcon.bin (12kb) file from the pack you downloaded of my link and placed the file into C:\Program Files\Jtag Tool\SMC then compiled freeboot using your original NAND dump?
4. You got no bad blocks or if you have you did remap them in your freeboot image before flashing it to the console?
1. check
2. check
3. my console is actually a zephyr so I used the zephyr files
4. I couldn't check for bad blocks since degraded won't open my nand
 
Jun 4, 2010
3,080
0
You can check in 360 flash tool .. Also double check if your original NAND still works fine by flashing it and then re-flashing freeboot.
 
Jun 4, 2010
3,080
0
Did you run your dump through NAND healer before all this? And did it change anything to it? I personally don't use it and last person posted on forums with a similar problems had his image changed using it and now he can't even get his console to boot the old dash as it altered his original dumps.

Can you boot your console into the old dash still?
 
1. check
2. check
3. my console is actually a zephyr so I used the zephyr files
4. I couldn't check for bad blocks since degraded won't open my nand
3. Zephyr SMC file won't work for you since your CB is 4570. Therefore, you will have to use SMC file for Falcon in order for it to work on your console.

4. Open the original NAND dump in 360 Flash Dump Tool and see if the Bad Blocks tab is shown. If not, you probably don't have any bad blocks. If it does, then see which Bad blocks you have.