[afzoo3hax]

Here is my connection diagram for the JSD-001 Motherboard. All of the pads are labelled exactly as they appear on the Teensy2.0++.

https://minus.com/lErO5BlFD33gs

Hope it helps someone.

[MJ999]

Originally Posted by afzoo3hax Here is my connection diagram for the JSD-001 Motherboard. All of the pads are labelled exactly as they appear on the Teensy2.0++. https://minus.com/lErO5BlFD33gs Hope it helps someone.

SUR-001, JTP-001, and KTE-001 have also the same testpoints.

[Gadorach]

I've been reading everywhere I can on how to get this PS3 downgraded, but nothing's working yet. Here's my setup.

DYN-001 + Samsung K8Q2815UQB-PI4B

Progskeet 1.2 (Used to get perfect dumps, which all matched. As the 1.2 can't write back, I'm trying to use a Teensy++ 2.0 for that)
Teensy++ 2.0 + NORway 0.6b3 + 3v3 from Console

Here's what's going on.

After I connected the Teensy the first time, using 30AWG Kynar at ~8cm, I was presented with Manufacturer Unknown (0x90) and Flash ID Unknown (0x909090).
I then proceeded to rewire everything with 26AWG, which yielded the very same results. Then I tried to switch the power source over to 5v to read the NOR, just to see if it would work. As such, I disconnected the 3v3 and powered down the console. In the off state, NORway returned (0xb4) and (0xf4f4f4) respectfully. If the console was turned on though, it returned to the previous (0x90) and (0x909090). I've since returned to 3v3 from the board and disconnected the USB power supply. If any one has some ideas, I'd love to hear them. Thanks for your time!

- Gadorach

[judges]

Originally Posted by Gadorach After I connected the Teensy the first time, using 30AWG Kynar at ~8cm, I was presented with Manufacturer Unknown (0x90) and Flash ID Unknown (0x909090). I then proceeded to rewire everything with 26AWG, which yielded the very same results. Then I tried to switch the power source over to 5v to read the NOR, just to see if it would work. As such, I disconnected the 3v3 and powered down the console. In the off state, NORway returned (0xb4) and (0xf4f4f4) respectfully. If the console was turned on though, it returned to the previous (0x90) and (0x909090). I've since returned to 3v3 from the board and disconnected the USB power supply. If any one has some ideas, I'd love to hear them. Thanks for your time! - Gadorach

First of all: don't cross-post your questions. And don't expect an answer within a couple of hours. Someone will answer eventually.

Have you tried using a voltage regulator? If you have one, try that first.

If you don't have one and your console isn't bricked (i.e. it boots to xmb), you can try this (Teensy fed with 3.3V from console):
1. Disconnect Teensy from usb, remove power cord from console.
2. Connect console to power, turn it on.
3. Let it boot to xmb and wait another minute.
4. Connect Teensy to usb.
5. "NORway.py COMx"
6. Check whether chip type is now recognized.
7. If it is, issue a "NORway.py COMx vwriteword patcheddump.bin"
8. If all goes well continue with the rest of the standard downgrade process (fsm, etc.)

I just figured that apparently some mobos don't supply 3.3V to the nor when tristate is pulled low at boot time. Hence the unknown chip type. But be warned, this is still experimental and you might have only one try to do this. If your console doesn't boot anymore after a failed write attempt or wrongly patched dump, you might have to power it externally by using e.g. an atx psu to be able to flash again.

-- judges

[Gadorach]

Originally Posted by judges First of all: don't cross-post your questions. And don't expect an answer within a couple of hours. Someone will answer eventually. Have you tried using a voltage regulator? If you have one, try that first. If you don't have one and your console isn't bricked (i.e. it boots to xmb), you can try this (Teensy fed with 3.3V from console): 1. Disconnect Teensy from usb, remove power cord from console. 2. Connect console to power, turn it on. 3. Let it boot to xmb and wait another minute. 4. Connect Teensy to usb. 5. "NORway.py COMx" 6. Check whether chip type is now recognized. 7. If it is, issue a "NORway.py COMx vwriteword patcheddump.bin" 8. If all goes well continue with the rest of the standard downgrade process (fsm, etc.) I just figured that apparently some mobos don't supply 3.3V to the nor when tristate is pulled low at boot time. Hence the unknown chip type. But be warned, this is still experimental and you might have only one try to do this. If your console doesn't boot anymore after a failed write attempt or wrongly patched dump, you might have to power it externally by using e.g. an atx psu to be able to flash again. -- judges

Thanks for the information, I'll try it shortly. Also, I do apologize, but I was planning to delete my post in this thread as I felt like it was hijacking over anything else. Hence why I started a new thread. I only found out that I couldn't delete my post after the fact. I didn't expect immediate help, that would've been completely unreasonable.

Else, as I was unaware that the ProgSkeet 1.2 wouldn't write to the NOR, I attempted it at first, and now the console does not boot, but instead either hangs at a green light or shuts down after a few seconds and blinks red. As I said though, I verified my dumps so it should be safe, but I'd assume that I now need to power the NOR externally in order to make it recognizable?

Again, thanks for your time and sorry for the misunderstanding.

Edit: Just thinking about it, but could I use the ProgSkeet to supply the required 3.3v for both the NOR and Teensy++?

- Gadorach

[judges]

Originally Posted by Gadorach As I said though, I verified my dumps so it should be safe, but I'd assume that I now need to power the NOR externally in order to make it recognizable? Edit: Just thinking about it, but could I use the ProgSkeet to supply the required 3.3v for both the NOR and Teensy++?

No, you cannot use progskeet to power nor and teensy. You would have to connect ps3's 3.3V and GND to an external power supply that is capable of providing at least 2A@3.3V. Teensy will also be powered by this. Of course console must not be connected to power cord. The thing is that you cannot just power the nor. Other parts receive power through the 3.3V rail as well, hence the 2A requirement.

But you can try this first: http://www.ps3hax.net/showthread.php...070#post284070

-- judges

[Gadorach]

Originally Posted by judges No, you cannot use progskeet to power nor and teensy. You would have to connect ps3's 3.3V and GND to an external power supply that is capable of providing at least 2A@3.3V. Teensy will also be powered by this. Of course console must not be connected to power cord. The thing is that you cannot just power the nor. Other parts receive power through the 3.3V rail as well, hence the 2A requirement. -- judges

Ah, so the ~500mA isn't enough, that's disappointing. I have a few ATX supplies I wouldn't have a problem with tearing down to get the power, but I've heard that the 3.3v from ATX supplies is only for sense, and therefore completely useless for power. Do you have any suggestions as to an item that would provide the required supply and would be readily available?

Edit: I should also mention that I tried the other method to no avail previously.
Edit2: I have multiple Xbox 360's here, do you think I could use one of the unswitched 3.3v outputs to power everything? That would be ideal, assuming it has enough of a load capacity.

- Gadorach

[judges]

Originally Posted by Gadorach I have a few ATX supplies I wouldn't have a problem with tearing down to get the power, but I've heard that the 3.3v from ATX supplies is only for sense, and therefore completely useless for power. Do you have any suggestions as to an item that would provide the required supply and would be readily available? Edit2: I have multiple Xbox 360's here, do you think I could use one of the unswitched 3.3v outputs to power everything? That would be ideal, assuming it has enough of a load capacity.

I'm not much of an electronics guy, so I can't give a definite answer to the xbox psu's. But as long as it's stabilized 3.3V, it'll probably work.

Guess it depends on the ATX supply. I've got an ATX2.0 supply here that provides up to 30A@3.3V. Just have a look at the label. You might also wanna check out this (load resistor required): http://www.ps3devwiki.com/wiki/Talk:...h_external_PSU

-- judges

[Gadorach]

Originally Posted by judges I'm not much of an electronics guy, so I can't give a definite answer to the xbox psu's. But as long as it's stabilized 3.3V, it'll probably work. Guess it depends on the ATX supply. I've got an ATX2.0 supply here that provides up to 30A@3.3V. Just have a look at the label. -- judges

My 250W ATX PSU here is rated at 14A on the 3.3v rail, which is amusingly higher than it's 12v rail, which is only rated at 8A. It only needs the soft switch tied to ground to start up, so I have it all set and ready. I'll try it out in a few minutes, when my soldering iron finishes heating up again. Thanks a bunch for the suggestions and, with any luck, this will solve my problem.

Ok, well, I got everything hooked up, and the power supply is outputting the correct voltage, but I'm still getting (0xf4) and (0xf4f4f4), which is what I got from the ProgSkeet powering it as well. I'm rather confused as 14.0A on +3.3v should be doing the job just fine. I've heard of others not being able to collect the NOR identity with newer versions, and some recommended 0.4b12. I was unable to locate that version, however, and therefore have no idea if that would work or not. If the chip was blank or full of garbage data, I'd still assume it would report it's chip versions just fine as well, so the ProgSkeet being retarded shouldn't have anything to do with it either. Any other ideas?

- Gadorach

PS. I have plenty of images, but as I'm yet to reach a 15-post count, I can't post any of them, or direct links to them. Should you wish to see my installation, here's a broken-up link to my album. Link: imageshack(dot)us/g/1/9969618/

[DebugBrain]

Hello, I also use teensy 2 + + from July 2011 I consider it the most reliable flasher available on PS3 (THANKS TO JUDGES FOR NORWAY VERSIONS!) I use a different setup on samsung K8Q2815UQB (even today) and I have always gotten good dump.

Teensy without voltage regulator,
no short on the 3v pad
not cut the track of 5v pad

If you've already cut the track pad 5v make a short to restore, (example in the attached immage!)


Connect the VCC pad on the motherboard to the 5v pad on the teensy, other wires according to the diagram

On samsung K8Q2815UQB I always use norway-04beta12!

Power cable connected, Ps3 off, usb cable disconnected!

PS: Now careful, these three steps should be done in quick succession
1) Turn on the ps3 from power button
2) very quickly connect the USB cable to the teensy
3) very quickly press and hold the power button, the ps3 immediately turns off, all LEDs off (this is normal)

unplug the power cable (not neccesary but better to do it)

type norway.py COM (your COM number) to verify that the NOR has been recognized correctly.
enjoy

This method works on ps3 with ylod and briked, no need to use an external power supply.
Note: In the example image shows a teensy 1 where 5v pad and 3v pad positions are inverted respect their position on teensy2++ board, not to be confused just follow the codes printed on the teensy2++ board

ps: sorry for my bad english!