Discussion in 'Help & Support' started by ps3xbox, Jan 12, 2020.
I dont know
A Bad Flash can also cause a YLOD or any incompatible Firmware Files or missing files.
Remember YLOD is a General Hardware/Software Indicator Failure, anything can happen
I completed the downgrade and it showed the firmware was on 4.21 but then after this it stopped turning on so i thougt it was a firmware problem so flashed original firnware back.
So the last firmware version running you saw was 4.21 ?
The exception of what i said before is if you do a successful downgrade... in that case your syscon is in 4.21 (and you flash dumps are from 4.8x something)
So by now forget about the tokins, you need to solve this software problem first, take a look at the readme and changelog texts of this tools:
The PyPS3rebuilder is to rebuild corrupted flash dumps using a donor flash dump (you dont need it because your flash dump is not corrupted)
Use PyPS3checker to scan your dump, is going to tell you the version of your "ros" regions in the dump (there are 2 ros regions in the PS3 flash dumps because the flash stores info about the latest firmware you installed and the previous)
You could use PyPS3patcher to replace the "ros" areas in your dump... the problem is the tool have the "ros" patches hardcoded for 4.85 version and you need the patches for version 4.21
So... not sure what to do, we can ask @littlebalup but as i said before, since you have a hardware flasher you should not get scared in writing stuff to flash because you could replace that data at any point
Originally i was on 4.8x and downgraded with hardware flasher but it showed up as 4.21 but thought it should bw 3.55. I checked system firmware through xmb and showed 4.21.
After this it was not turning On even with applying heat so flashed patched dump but no luck
I thought then flash original dump and see
What do i do
But after replacing these nec tokins its really trying to start but fails
I guess as long as u use the hex reader to verify the cfw pup file, check and compare it with a known good working one and they both pass as identical it should be fine?
The system isnt starting. How can i install cfw
u dont need the console to start to check the pup files. this is to double check what u flashed and installed originally was good.
When you was downgrading you had a PS3 game disc inserted in the bluray drive ?
All the PS3 game discs contains a firmware update (with a version that matches the release date of the game)
When you install a firmware, from USB, network, whatever... there is a point where the PS3 does a reboot and it takes the upate from the disc
Maybe at that point the tokins started failing again
From this point im not sure what happened exactly, which patched dump ?, the one patched for 4.8x with the NoFSM patches ?
Scan that dumps, you need to know the exact firmware versions... just by telling 4.8x is not good enought
Ok, so I have been going through the dumps
I dumped the original nand and the details are below.
ROS 0: 4.81
ROS 1: 4.80
So I then patched this to 3.55 using the FSM method but then once It completed, I removed the clip and re-assembled and turned on but I got the blinking red light and beeps problem so thought this was normal, not sure. I applied some heat through the vent., no joy so I thought I would continue. I used the teensey as a FSM dongle and done the power, eject sequence but did not get into the service mode.
So I put the get into fsm files onto a usb stick after triggering FSM mode in the right USB port and I turned on. It accessed the USB stick and saw the ps3 hard drive led flash, but red light and beeped
Gave some heat from a hair dryer and it did turn on but I was in FSM mode
I then used the exit FSM mode files and it did boot into xmb but was on version 4.21, which was strange. I thought this might be spoofed, like a downgrader firmware so tried to put 3.55 through recovery mode but did not work
I dumped the firmware like this and looked at the ros and it was showing that
ros 0: N/A
ros 1 : 3.55
So I took my original dumps and patched using non fsm method and checked again using tool, before flashing and got
ros 0: 4.50
I wrote this back and turned on, again got red blinking light with beeps. I put heat from hair dryer but cant remember if it booted to xmb or not
Since this time it has not been starting, always getting red light with beeps
I thought at this point to reflash original 4.81 dump and start over
but I flashed just normal flash and the console did not start
I erased nand and flashed again 4.81 original and again did not start
I started thinking if it was turning on with the hair dryer then it must be the NEC / TOKIN.
I have replaced all the nec tokin on one side of the board ( the side without the CELL and RSX), comparing to how it was
It seems like the fan is running longer and trying to start but red light and beeps.
Before the nec / tokin replacement the fan would spin less than now but red light and beep
I used the downgrade guide, from a well known person on another forum
If you're original dump does not work then its not a good dump or you are not flashing it back correctly. Start off by getting back to working ofw 4.81. Then use the software web exploit to patch it. Much simpler.
It sounds like you bricked it with the first flash.
Is your original dump checking ok?
My original dump is check ok
Can you guide me on what to do pls
I dont know how I could have bricked it
I dumped the nand and checked it with a checking tool and said ok
When i flashed back it said no errors and got the nothing to flash when done
I dont know how to help. Flashing your original dump back should work.
I've never seen one red light issue that's been flash related and I've repaired hundreds. In my experience red light is a hardware issue.
If you get a delayed redlight, its an nec token issue. If you replace a token and the delay increases you are on to something. Keep changing tokens and it should fix.
If it's immediate red light I would look more at GPU or cpu contact or a power issue. Never reflow. Its a waste on ps3. Only a reball is a long-term effective repair.
OK, but then what happens to your consoles when they are bricked through a bad flash?
This sounds 100% like any software brick I have ever heard of.
Can some one help me unbrick, please
I will really appreciate it
I don't think there is help for you to be honest, If your original dump is checking OK but still won't work when flashed back I do not know how to help you.. Sorry
I really hope you did not manage to enter fsm on 4.21 ofw either.
I don't know why you didn't just use a Web exploit when on 4.81.. So much simpler.
Thinking about it, the console died directly after flashing it and reassembly. So it's either the flash that bricked it, or you damaged the hw somehow.
Go over the main board really carefully and look for damage... I don't know after that. Its unlikely that a tokin failed just as you flashed it in my opinion.
I checked the original dumps and they are ok
When I patched the dumps, I patched using FSM method, 3.55 so I assume it was on 3.55
I have been reading about the CoreOs patch for bricked consoles
would this work
Bad flash causes ylod. On nor consoles you ground tristate to confirm. If the console then stays on, 100% confirmed its bad flash.
This doesn't work on ops NAND console. Grounding tristate has no effect.
Op has an early phat NAND and has been exposing it to added heat with a hair dryer. These already have poor heat dissipation due to the larger cpu and GPU than other models. Its overheating, not flash, gauranteed.
Separate names with a comma.