this is my first post here just joined.
i bought a a 3key yesterday for my dusty ps3 cech 2505 b. turns out to be the wrong one didn't have the one i wanted in stock.
so now i have a e3 flasher.
now the problem i have is im on 4,46. i believe i can downgrade. the MinVerChk i downloaded doesnt seem to work.
the next problem i have is that i have a 12 year old coming tomorrow with his 2502 a/b? with big expectations.
i think i can do both with what i got.
please if someone could point me in the right direction i would appreciate it.
ok 3.56 i can downgrade too. (ps3/update) this might take me a while...
installing e3 flasher now...
now installed and ps3 started.
What did MinVerCheck tell you? If your "Base Firmware" was only 3.60 and NOT 3.55 (OR LOWER!) then you are just SOL!... EOL!...
Originally Posted by ashraft
I never heard of MinVerCheck ever having failed in the way your are describing. Sadly the 25xx contains SOME of the last... AND THE VERY FIRST Versions of the PS3 that can.... OR CAN NOT be downgraded.
My only guess is if, MinVerCheck really did let you down, then you likely have a 25xx with the newer Metldr2 (Metloader v0.2), WHICH CAN NOT BE DOWNGRADED.
You may want to flip your PS3 over and checking the Spine Sticker for your DATECODE... (See attached.)
You can then compare your DATECODE with the List HERE: http://www.psdevwiki.com/ps3/Date_Codes
If your lucky you might be able to do something with it....
If not then you can always install an ODE like Cobra, E3 or PS3K3y.
make a dump and upload it to mediafire.com
email it to email@example.com and ill have a look at it and let you know your options
ive read reports of ps3s that are datecode after first quarter of 2011 that do not use metldr.2, so best thing to do is check the dump itself ;)
, what model does the 3key work for?
While that is in itself very true.... I'd be less inclined to recommended someone to drop actual Cash on an E3 Flasher, when their chances, albeitly greater then Zero... Are still very much less then One, that it will all somehow workout for them, and that they can actually find that they were be able to install CFW all along. Sadly without an E3 Flasher (or for that matter a ProgSkeet or a Teensy++), there is just no simple way to find out!
Originally Posted by No0bZiLLa
And assuming that they had a PS3 that could only be rolled back to OFW3.60 (with the old metldr vesion BIG ASSUMPTION TO MAKE BTW!), they'd still have to fallow an entirely different method to Downgrade Method(s), to the Ones found here, and elsewhere, based on the very same Method. Which would likely lead the poor buggers to brick their PS3s! [Again an update to the Balieyscream HOWTO would seem to be in order here!]
But, sometimes I get the felling that some of these "kinds of Posts" are, looking for a glimmer of hope where there might not be One. I suppose the best thing would be to know someone with an E3 who could check it for you. But, lets not assume that the E3 Flasher is so affordable to be a throw away product. When it costs like 70.00€+. That can (or should), be thrown away on such an unreasonable bet.
Has a list of Valid Metldr / Bootldr offsets... As well as all the Invalid Ones so you can use HxD to quickly eyeball it for yourself.
he already has a flasher... and i wouldnt tell someone to spend money on a flasher in this situation either. they would be better off to sell said ps3, and just get an exploitable one or one thats already exploited.
Originally Posted by ashraft
please turn the console back off, then copy this e3 flasher update to your micro sd card and put the sd card in the e3 flasher.
flip switches 12 down and 3456 up
turn on the ps3 and all 8 blue leds should light up.
then after the ps3 is booted, make a dump with 12 down 3 up 456 down (all down except switch three up)
this will make a dump onto the micro sd card.
email the dump to firstname.lastname@example.org or just check it yourself ;)
also another FYI, here is ps3devwiki's e3 flasher page, it will help ya with the settings on the flasher and maybe help you understand any errors you get ect
Yeah well... The response had less to do with Op per-say, then as my overall general opinion on such matters.
Originally Posted by No0bZiLLa
And its feels all to easily like leading such punters up the proverbial Garden Path. The last thing I want to do is to give someone poor advice that, when poorly executed will kill their PS3. Sometimes its their fault for not being forthcoming with what they have ex. a 25xx or they are just plain dumber then a Bag of Hammers. At the risk of being a total arsehole and, a Jerk. There are some Poeple that shouldn't try to downgrade their Devices when they have absolutely no idea with which they are getting themselves into. Or fully appreciate all the risks involved.
However I do wish Op the best of luck though...
first of all would like to thank all for your replys.
my problem is now sorted.
quick run down
1 had a 3.56
2 i bricked due to not having the right nor patcher.
3 learned to solder.
4 sbe to TRISATE
6 brick still wrong patcher.
7 sbe came of ribbon had to go to ground on m/b
8 another brick. still never worked out the patcher.
10 the right patcher
11 restarted ps3 twice before downgrade dongle lit up.
12 stayed red never changed restarted ps3
i only had 1 dump so think i was lucky (youtube never told me to take more or check them)
i liked your last post ichijoe
Originally Posted by Ichijoe
I probably saw the same YouTube. Where the Guy gets to the point... Oh yeah this next step is very IMPORTANT! But, never goes on to say just what it was... Then goes on later in the Video and says that that "Part" wasn't as IMPORTANT as he at first implied...
That's cause [sic] YouTube Op already had a confirmed & working Backup of his ROM. When you have that IN A VERY SECURE PLACE! IMHO On a disused USB Stick, that contains other sensitive long term storage Documents (i.e. Copies of Wills, etc.. etc..), which then should be kept in a Fireproof Box away from "Other hands" = Secure! Then you can afford to be that blase about taking, and making proper Backups.
Needless to say I managed to post that message in a response to said YouTuber, and got flamed for it hard too...
You always need to take a few examples, to then compare the MD5 Hashes to see that what your "Pulling" is the same set of ~hopefully~ uncorrupted Data. You then need to go though EVERY EXAMPLE from the HOWTO, and the PS3 Dev Wiki (Validating Dumps). By Hand or Eye. Then, ignoring any inconsistency One finds with their ""00" Statistics" (i.e. 18.23% instead of +18.24%), where EVERYTHING ELSE checks out!
Then, and ONLY THEN! Do you even consider pulling the Trigger on flashing your whatever it is, in this case a PS3. But, again this MESSAGE applies to any Device you plan to modify on the Firmware Level, not just the PS3. And when you do decide to "pull the Trigger" you have to accept that in doing so you might be killing your PS3. Again that's the risk you take.
Taking multiple examples of your ROM Dump to check their consistency, plus inspecting all the Code! WHICH IS EVEN MORE CRITICAL FOR 25xx USERS! Will lessen your risk substantially. But, there's never such a thing as 100% a 100% of the time. Or why would we even need to worry about this SBE thing?
In any case.. Congratulations on having successfully downgraded your PS3.
BTW: Did you remember to replace your Thermal Paste on the CELL And RSX Chips? The last thing you want to do is to run those dry. Or with the stock white gunk it came with. Doing so will definitely kill your PS3 faster...
no i haven't . still the stock white gunk. will do it on the weekend. will be attempting my second on sat. at least im more prepared this time. its an older model than mine so should be fine. thanks again