Verify error with NORway

LizZo

LizZo

Member
Hi american friends :D
I am here to ask support about NORway.
I have several dumps of my NOR, and i am able to write them. They are verified with PS3Dump checker.
At the end of the write process, the verify fails imediatly, so there is something wrong.. The PS3 is still bricked, i don't understand if the write process is not completed or there is another problem with the teensy..

Can anyone help me to figure out what's wrong?
I have this problem since a brick caused by a test for a 484 CFW.. i tried a lot of times to write and verifiy, with the normal write command (this is a little bit bugged i think, the task take a lot of times, more than 2 hours..) and also the writeword command.

Thanks in advance,
and happy holidays to all of you!!
 
littlebalup said:
Try writewordubm command
Click to expand...
Thanks for the reply, but the verification still fail..

Screenshot-1.png
 
Try the commands starting the name with a "v", this way... "vwrite", "vwriteword", or "vwritewordubm"

Are the same commands than the standards, but the "v" added at the begining is going to trigger a verification after the writing process is completed
What that verification does is mostly a flash dump of the data that has been written... and compares it with the "source" file in your PC

It takes double the time to complete though, because are doing a write + read consecutivelly
 
Last edited:
You may have a faulty chip. Make a new dump after the write and compare yourself with hex editor to see where the issue is. And double check your solders, etc...
 
sandungas said:
Try the commands starting the name with a "v", this way... "vwrite", "vwriteword", or "vwritewordubm"

Are the same commands than the standards, but the "v" added at the begining is going to trigger a verification after the writing process is completed
What that verification does is mostly a flash dump of the data that has been written... and compares it with the "source" file in your PC

It takes double the time to complete though, because are doing a write + read consecutivelly
Click to expand...
I tried these commands, and the results are the same. With the 'v' the verify starts before the write process, and this is what happen:

BTW, i used this teensy for a year, and it was perfect.. Since that day i am no more able to write a dump..

Screenshot-2.png
 
Hmmm, are you sure you have the correct versions of python and pyserial ? (and not the modern ones)
As far i know it requires python v2.7 and pyserial v2.5
 
littlebalup said:
You may have a faulty chip. Make a new dump after the write and compare yourself with hex editor to see where the issue is. And double check your solders, etc...
Click to expand...

The dump after the write gives me a strange file.. looking into a hex editor it appear very different from my dumps.. what's the problem? Is the teensy broken?


Inviato dal mio iPhone utilizzando Tapatalk
 
I doubt it if you can dump. Do you use a clip or direct solders? What version of norway? Do you use the console power supply + tristate point? And you should double check the WE# (write enable) connection, the RY/BY#, RE, OE, etc.
 
What i would do if i where you is to use the read and write commands with small chunks of data, all the commands allows to configure an offset and lenght
Just try to write a few bytes, lets say... 16 bytes filled with 0x13371337133713371337133713371337 ... then read them to see if you got the same data

Right now the contents of the flash are corrupted, so writing some garbage in it is not going to cause any bad
And you have valid flash dumps so at some point all that gargabe is going to be cleaned up when you restore the full dump


*I was also thinking in the #WE wire... it means "Write Enable"... without it you are not writing anything because you are not enabling it
 
You must log in or register to reply here.

Similar threads

Back
Top