[sade050]

so i installed rogero on recovery after that my ps3 goes off itryed to turn it on but it turn off after 2sec so ichanged the hard disk and worked but its asked me to put 4.30
so the problem is can i install rogero 4.30 or only 4.30 ofw?

[w0313]

@sade050 your original firmware please,mention it?if you're on OFW 4.30 surely you got to install it. just info CFW 4.30 cannot be installed on OFW 4.30 yet you have to downgrade to 3.55 first in order to install it. what model is your PS3 anyway?

[sade050]

IWAS ON KMEAW 3.55 then intalled rogero 4.30
PS3 MODEL 2504B fw base 3.50

[w0313]

If you had enough money to downgrade with a flasher, then you have to update it with OFW 4.30 so you can downgrade it back to Kmeaw and try to update again to 4.30 CFW. If you don't, try the CFW 4.30.PUP and see what the result is.

[carldenning]

Originally Posted by w0313 If you had enough money to downgrade with a flasher, then you have to update it with OFW 4.30 so you can downgrade it back to Kmeaw and try to update again to 4.30 CFW. If you don't, try the CFW 4.30.PUP and see what the result is.

WTF u on about flasher and updating to 4.30 ofw



anyway @sade050 try installing the cfw 4.30 if that dont work then try the downgrade pup file which should work .

[w0313]

@carldenning sorry boss, I gave him two choices but the worse is with the flasher thing, since his PS3 Model can be downgraded though. fix my words if I'm wrong boss. thanks

[haz367]

u must try the Rogero 430CFW first, it should take it, assuming u come from kmeaw355, would be weird otherwise

i tested it for u to check what it ask for on Rogero 4.30 in Recovery, it's asking for 4.30 as its asking on ur side

for e.g Rogero 1.09 it ask for 421(the unspoofed version) for downgrade then use 420to355
if u then install rogero 3.7 from recovery to get back to 355 it ask for 4.40
this is the same on 4.30 rogero after using 425to355 pup

[sade050]

so idont need to flash it just dawngrade with rogero method ?

[haz367]

Originally Posted by sade050 IWAS ON KMEAW 3.55 then intalled rogero 4.30 PS3 MODEL 2504B fw base 3.50 so idont need to flash it just dawngrade with rogero method ?

flash? why flash like carldenning told u.... ur coming from kmeaw(maibe also QA flag it first before moving to >>>) or it must be HDD, also a little strange if happens all of a sudden....

anyway, it takes the spare HDD and asking for 4.30
it is tested that Rogero 4.30 asks for 4.30 in recovery, so that is correct and ur ps3 is asking for that, if only accepts OFW, the quoted message is wrong..right?



EDIT!

just noticed this post in the Rogero 4.30 topic about SLIMS/HDD corrupts etc..
i have not 4.30 on SLIM installed, 1.09 is good, FAT cechl04 so far good not having the hdd corrupt errors, just posted this in a hurry, seeing u have a SLIM 2504B, hdd problem, looks the same

Originally Posted by alexander123 A user on the forums at Tortuga posted this in response to needing to change a hard drive while on this Rogero 4.30 CFW. Hi. I Fixed the bug for my Slim 2504-B, datacode 0C. Let me explain, what it does seem to me. I think it's very important. All NOR consoles are affected, and are vulnerable. This is a serious thing. It's just a time bomb, a matter of time you get a semibrick if your HDD gets damaged on a NOR console (al PS3 Slim and some FAT consoles seem to be affected). There's many people affected. You won't be able to reflash or replace the HDD by a new one. The problem with this firmware, once you look inside, is that the LV0, LV1 and LV2 chains, seem to have been taken from the E3 firmware, which I don't understand. And the LV0 chain is broken because of the coolboot and the logo of Rogero's 4.30. This means, that if you flash this firmware on a NOR console and then format the HDD because the data is corrupted or because you want to do it(or simply you try to put a new one), you get in a loop, a semibrick. The brick is because the format is not being done correctly, cause of the bad lv0 string. The way I fixed it is taking the HDD of the console, putting it on a PC, and destroying all the format. Then managed to get into a recovery that detects the HDD without format and flashed the 4.25to3.55. The console asked to reformat about 2 times more, but it came to alive with the semi-downgrade done. The NAND consoles are not affected, but the broken chain is there and who knows. cheers. Can anyone confirm if this is the case and there is a possibility of a future semi-brick if updating to this 4.30 CFW? I want to thank Rogero for his work and by no means want to start up any rumours if not true...just want clarification before I jump and install this over my KMEAW 3.55 CFW.

[sade050]

Originally Posted by haz367 flash? why flash like carldenning told u.... ur coming from kmeaw(maibe also QA flag it first before moving to >>>) or it must be HDD, also a little strange if happens all of a sudden.... anyway, it takes the spare HDD and asking for 4.30 it is tested that Rogero 4.30 asks for 4.30 in recovery, so that is correct and ur ps3 is asking for that, if only accepts OFW, the quoted message is wrong..right?

THIS IS THE STORY
first i QA my ps3 when iwas on 3.55 then intalled rogero cfw 4.30 with recovery menu but in the middle the ps3 turn off tried to turn it on but it goes off after 2sec so i changed the hdd and worked its ask for 4.30 fw soory for my english
ps i plug my hdd with pc and its work then i put it in the ps3 and it same problem the ps3 turn off after 2sec