[sguerrini97]

Originally Posted by TizzyT Yes that it, I just peel each wire off and use them to solder, it works very well for me at least. Ask around if you would like and get opinion on it. If you need a larger size use a floppy cable they work as well. I don't solder a lot but when I do I use those as its easy to work with.

I have 40 wires of 14 cm. I need more? How should be long each wire? Thanks.

[TizzyT]

Originally Posted by sguerrini97 I have 40 wires of 14 cm. I need more? How should be long each wire? Thanks.

I am sorry I have never used a teensy nor have I soldered to one, I've only suggested the type of wire you might be able to used. @judges seems to be of more help. Again I'm sorry.

[sguerrini97]

Originally Posted by TizzyT I am sorry I have never used a teensy nor have I soldered to one, I've only suggested the type of wire you might be able to used. @judges seems to be of more help. Again I'm sorry.

Don't worry
I take an old Floppy Cable long abount 50cm and with it I make 33 wires :D

[judges]

I've updated norpatch.exe to recognize the new OFW 4.11 in your dumps. You'll find the download link in the 1st post of this thread (github)...

-- judges

[jjblaster3]

hi
ok so i used this tutorial to create patched core_os..

http://www.nextgenupdate.com/forums/...-purposes.html

the file size required by norpatch is 7340000 bytes and the one i get is around 5212154 bytes..

is there something i am doing wrong? could someone please post or pm me a link to a patched 3.55 core_os so i can use norpatch to patch my dump?

p.s i used dospiedra's v2 nor patching method and it works, but only with rogero v2 firmware.. all other ones i install (in service mode or not, patched lv1 checks or not) give me yellow/red light of death..
but, when i reflash my patched dump, the firmware works..
so i figured the problem comes up when installing the firmware, the nor is modified somehow and this is affected by the dospiedra patch which causes yellow/red light of death.. so im guessing this method is not the way to go?

[judges]

Originally Posted by jjblaster3 hi ok so i used this tutorial to create patched core_os.. http://www.nextgenupdate.com/forums/...-purposes.html the file size required by norpatch is 7340000 bytes and the one i get is around 5212154 bytes.. is there something i am doing wrong? could someone please post or pm me a link to a patched 3.55 core_os so i can use norpatch to patch my dump? p.s i used dospiedra's v2 nor patching method and it works, but only with rogero v2 firmware..

I've never used any of those tutorials, so I don't really know what the results are.

But if your cos.bin doesn't have the required size, you probably missed step 7 from your linked tutorial. You need to unpack/decrypt your cos.pkg first. Although I don't really see the point in using MFW builder to apply the patch if you afterwards have to replace lv1.self manually in your cos.bin (shouldn't MFW builder already have done this?). But as I said, I've never done it like that.

Btw, once you've flashed a patched cos.bin to your ps3, you should be able to install any kind of CFW (patched or not) in FSM.

[kabeero]

Hi,

I'm having trouble w/Teensy2++ and Samsung K8Q2815UQB running NORway 0.4 beta 12.

I'm able to dump and issue erasechip while console is in standby, or unplugged with
CrackMyDay's method

I'm not able to issue writeword or writewordubm commands in any mode (on/standby/unplugged). I've tried with the power regulator installed and console in standby, which worked for dumping, but this errors out after about 1200 KB/16384 KB. I've tried removing the regulator as per CrackMyDay's method and cannot issue either write command.
This is the message I receive:

__main__.NORError: Ping failed (expected 42, got ff)

I'm not sure if this message is indicating that my Teensy is crashing, or if the NOR is overwhelmed and stopped responding to pings. I've looked at the NORway.c Teensy code and it appears that on ping attempts no data is going between Teensy to NOR, so I'm thinking that it's the first case.

I've hooked up my ~OE (0), ~CE (1), ~WE (2), RY/~BY (3), and A22 (4) lines to a logic analyzer and got this output while issuing writewordubm. The failure occurs around the part of the graph where A22 goes high, and the write halts at about 1100-1400 KB/16384 KB with the Python error shown.

Does anybody have any ideas on what may be my problem? My final resolution is to replace my Samsung chip with a Macronix MX29GL, but I'm not sure if my dump and PS3 (CECH2001A) will be compatible.

Thanks for any opinions or ideas


SOLUTION:Don't use Linux.
After installing Python 2.7 on a Windows computer with Teensy drivers, this Python error went away.
I was able to leave the regulator installed and not have to connect the Vdd on the NOR chip to anything, able to write with PS3 on standby.

[jjblaster3]

Originally Posted by judges I've never used any of those tutorials, so I don't really know what the results are. But if your cos.bin doesn't have the required size, you probably missed step 7 from your linked tutorial. You need to unpack/decrypt your cos.pkg first. Although I don't really see the point in using MFW builder to apply the patch if you afterwards have to replace lv1.self manually in your cos.bin (shouldn't MFW builder already have done this?). But as I said, I've never done it like that. Btw, once you've flashed a patched cos.bin to your ps3, you should be able to install any kind of CFW (patched or not) in FSM.

thanks for the help, i did not actually use that method per say, coz they already provided one patched for us, but the link was dead so i probably found a corrupt version or sumthn in other sites

oh and also since im not able to install any other firmware apart from rogero v2, i guess its the fault of dospiedra's method..

will try out all scenarios, thanks again

[cvp]

--delete--

[sguerrini97]

@judges i've got a problem: i have solder a wire on the NOR Vcc bur i made it wrong, so i removed the solder but also the already existing solder on the motherboard gone away.. Here is a photo:

What can i do? Thanks and sorry for my english.