[Sorah]

Hello everyone.

So yesterday I finally got my e3 flasher. I was in 4.11 OFW and "upgraded" to Rogero 4.30 CFW. I spent some time trying things out and after rebooting it asked me to connect the controller and install a FW over 4.30. By mistake I installed the 4.31 MiralaTijera CFW.

Now I have some problems/questions:
1. Is there a way to downgrade it back to Rogero 4.30? (I don't have a dongle)
2. I installed multiMAN 04.18.00 FULL and everytime I start it I get the following error: "multiMAN cannot enable BD-ROM emulator. Functionality may be restricted. Error: Unsupported system firmware"
3. I've been trying to save BF3 into my internal hard disk. But everytime I start it, the XMB menu appears without the CD icon. I tried with with /app_home/PS3_GAME/ but everything I get is a black screen. Is that because of the error I get while starting multiMAN?

Thank you all!

[w0313]

1. Use Rebug Downgrade.PUP
2. Install/Update to the latest MultiMan, it should fix your problem
3. Back to number 2 and set the BD Mirror to ON and play it with disc

[haz367]

Originally Posted by Sorah So yesterday I finally got my e3 flasher. I was in 4.11 OFW and "upgraded" to Rogero 4.30 CFW. I spent some time trying things out and after rebooting it asked me to connect the controller and install a FW over 4.30. By mistake I installed the 4.31 MiralaTijera CFW. Now I have some problems/questions: 1. Is there a way to downgrade it back to Rogero 4.30? (I don't have a dongle) 2. I installed multiMAN 04.18.00 FULL and everytime I start it I get the following error: "multiMAN cannot enable BD-ROM emulator. Functionality may be restricted. Error: Unsupported system firmware" 3. I've been trying to save BF3 into my internal hard disk. But everytime I start it, the XMB menu appears without the CD icon. I tried with with /app_home/PS3_GAME/ but everything I get is a black screen. Is that because of the error I get while starting multiMAN? Thank you all!

assuming all went correct and u now running "4.31 MiralaTijera CFW" u can safely downgrade back to 3.55 first! using the rebug's 3.55.4_999 downgrader.PUP, if u not qa flagged the console, do it at this point after using the 999 downgrader..!! then install e.g 3.55.4 rebug original and go up again to any prefered cfw

for the MM error its because that build had no support for the new 431CFW, so either update MM to latest = 04.19.04(04.19.00 >>)

or if u like to test the Core "flags" out from that 431CFW, extract MM and place "AIOMOD.BIN" into the "payloader" folder on root USB nxt to cellftp.self/copy_script.txt and the "flags" folder where u drop the "payloader" flag, then on booting the ps3 with MM 04.18.00 takes the payload thats running in memory and u have working MM = sc36-Hermes payload..easier to update anyway..

important factor here cuse u never downgraded to 3.55?? and went straight to 4.30 rogero using three musketeer patches? then u never dehashes(toggle_qa-install 2xOFW355 = proper dehash) so if u decide to go down to 3.55, make sure u qaflag/dehash the ps3

dont go straight from 431 to 430 rogero wich would not wotk (i guess)

good luck

[Sorah]

Originally Posted by haz367 assuming all went correct and u now running "4.31 MiralaTijera CFW" u can safely downgrade back to 3.55 first! using the rebug's 3.55.4_999 downgrader.PUP, if u not qa flagged the console, do it at this point after using the 999 downgrader..!! then install e.g 3.55.4 rebug original and go up again to any prefered cfw for the MM error its because that build had no support for the new 431CFW, so either update MM to latest = 04.19.04(04.19.00 >>) or if u like to test the Core "flags" out from that 431CFW, extract MM and place "AIOMOD.BIN" into the "payloader" folder on root USB nxt to cellftp.self/copy_script.txt and the "flags" folder where u drop the "payloader" flag, then on booting the ps3 with MM 04.18.00 takes the payload thats running in memory and u have working MM = sc36-Hermes payload..easier to update anyway.. important factor here cuse u never downgraded to 3.55?? and went straight to 4.30 rogero using three musketeer patches? then u never dehashes(toggle_qa-install 2xOFW355 = proper dehash) so if u decide to go down to 3.55, make sure u qaflag/dehash the ps3 dont go straight from 431 to 430 rogero wich would not wotk (i guess) good luck

Thank you for your reply.

I actually never downgraded it to 3.55 because (as you guessed/knew) I used the musketeer patch. To be honest I didn't understand everything you told to me and because of that I guess that the easiest way is to downgrade and upgrade my PS3 again.

So.. should I launch "Toggle QA"? Do I have to use "3.55.4_999 downgrader.PUP" (where do I get it from, didn't find it on google)? And after that? Will I be able to install 4.30 Rogero again? Do I have to change some switches on the e3 Flasher board and will I be able to dual boot?

Sorry for all the questions and thanks

[haz367]

Originally Posted by Sorah Thank you for your reply. I actually never downgraded it to 3.55 because (as you guessed/knew) I used the musketeer patch. So.. what should I exactly have to do after launching "Toggle QA"? Do I have to use "3.55.4_999 downgrader.PUP" Sorry for all the questions and thanks

no problems...although for "dual boot" i cannot help...

for ur other question, its easy
if u never downgraded to 355 as u did...now first downgrade using the 3.55.4_999 downgrader, qa flag it > run toggle_qa 1 time only, it triple beeps and reboots automatically, now verify the qa flag = hit L1+L2+R1+R2+d-pad down+L3 all together on "network settings" u get 3 new settings = qa toggle active

then simply dehash the console using Rebug original 3.55.4 from XMB - system update OR from Recovery using any other 3.55(OFW/CFW) then ur free to go up&down&up again so yeah u can go back to latest Rogero 4.30 2.05 from this point

[Sorah]

Originally Posted by haz367 no problems...although for "dual boot" i cannot help... for ur other question, its easy if u never downgraded to 355 as u did...now first downgrade using the 3.55.4_999 downgrader, qa flag it > run toggle_qa 1 time only, it triple beeps and reboots automatically, now verify the qa flag = hit L1+L2+R1+R2+d-pad down+L3 all together on "network settings" u get 3 new settings = qa toggle active then simply dehash the console using Rebug original 3.55.4 from XMB - system update OR from Recovery using any other 3.55(OFW/CFW) then ur free to go up&down&up again so yeah u can go back to latest Rogero 4.30 2.05 from this point

Thank you once again.

As soon as I start Toggle QA I get the error 80010017. Is there some way to fix that?

[haz367]

hmm..toggle_qa.pkg...on the 3.55.4 rebug?
incase here's the original toggle_qa
http://rghost.net/43592726

anyway...try this way..
go into package manager and install the latest Rebug Toolbox from hdd0\packages..
run it and go the last options and "enable" QA from there

works? let us know..

[DEFAULTDNB]

Sorry to interject, I have what could be a silly question, and perhaps I have missed something:

and went straight to 4.30 rogero using three musketeer patches?

I actually never downgraded it to 3.55 because (as you guessed/knew) I used the musketeer patch.

@Sorah never specified what PS3 model they have, so how do we know they CAN downgrade to 3.55 to dehash?

If the min FW praxis is 3.56+ then how can they dehash?

(just read through @Sorah s old posts and dont see a mention of a PS3 model)

[haz367]

ah nice observation there we wait for him to reply...

[Sorah]

Originally Posted by haz367 hmm..toggle_qa.pkg...on the 3.55.4 rebug? incase here's the original toggle_qa anyway...try this way.. go into package manager and install the latest Rebug Toolbox from hdd0\packages.. run it and go the last options and "enable" QA from there works? let us know..

What if I told you that it doesn't? ^^"
It shows me the same error.