Sponsored Links

Sponsored Links

Page 7 of 9 FirstFirst ... 56789 LastLast
Results 61 to 70 of 90



  1. #61
    Senior Member mushy409's Avatar
    Join Date
    Oct 2008
    Posts
    329
    Sponsored Links
    Sponsored Links
    Quote Originally Posted by sk group View Post
    heads up to future downgraders:

    you can semi-brick your ps3 if you update incorrectly or mess up the process. you then won't be able to turn on the ps3 as it will just give you an almost musical beep.

    you will also not be able to turn off service mode with the second self file either. nore can you update again as youve most likely turned off the ps3.

    the fix is simple though, just hard reset it and try to re-enter service mode. sometimes it won't work and sometimes it will - it took me two tries. when youre in service mode (you can only tell by the dongles light) - try the whole process again but use the modified 3.41 update.
    What about if you have made NAND backups with infectus? Can you just restore the backup of the 3.50 firmware? I'd be willing to try this - I already have made backups of my 3.50 console...

  2. #62
    Senior Member BwE's Avatar
    Join Date
    Apr 2010
    Posts
    709
    Sponsored Links
    Sponsored Links
    I made a video for some reason, also i forgot to film it in portrait.




  3. #63
    Registered User MSPARKY83's Avatar
    Join Date
    Mar 2006
    Posts
    13
    Sponsored Links
    Sponsored Links
    Just curious mate, but did you ever get your ps3 console working again after semi-bricking it? I haven't gotten my e3 in the mail yet, but was curious as it would royally suck if you have to get a new one. Cheers, and I hope all went well.

  4. #64
    Senior Member BwE's Avatar
    Join Date
    Apr 2010
    Posts
    709
    Quote Originally Posted by MSPARKY83 View Post
    Just curious mate, but did you ever get your ps3 console working again after semi-bricking it? I haven't gotten my e3 in the mail yet, but was curious as it would royally suck if you have to get a new one. Cheers, and I hope all went well.
    yeah buddy it's easy to fix. i deleted that video to make a better one.

    i'll show everybody the REAL bricking - i only did the failed downgrade bricking.

    i'm going to write garbage to the flash

  5. #65
    Registered User MSPARKY83's Avatar
    Join Date
    Mar 2006
    Posts
    13
    Lol, that's good. I just wanted to note here as well, if you replace the 3.41 pup with the original 3.50 pup, this will also save you from a semi-brick. Not only that, but your console should still be in service mode as well. So that should help anyone else who may or may not be experiencing this problem. Cheers!
    Last edited by MSPARKY83; 12-06-2010 at 12:33 AM

  6. #66
    Senior Member BwE's Avatar
    Join Date
    Apr 2010
    Posts
    709
    lol i've just discovered the lowest firmware you can goto - took me ages to work it out.

    it's surprisingly not that low

    i'm going to do research on debug now <3

  7. #67
    Registered User MSPARKY83's Avatar
    Join Date
    Mar 2006
    Posts
    13
    Are you referring to the lowest debug, or the lowest retail firmware? I know that you can install debug 2.15 firmware, and retail 3.15. I would love to know what else is possible. ^_^

    btw, be careful when flashing the debug files it will change your SHA1 hash encryption.

    Sorry for the double-post, but for some reason I can't edit my last one.

    If you do happen to flash to 2.15 debug firmware, I would love to know if your able to come back from it to a retail firmware. On behalf of myself, and i'm sure the rest of the scene, thank you for your contributions in testing. Its greatly appreciated!
    Last edited by MSPARKY83; 12-06-2010 at 12:50 AM Reason: Automerged Doublepost

  8. #68
    Senior Member BwE's Avatar
    Join Date
    Apr 2010
    Posts
    709
    what gives you the impression you can get 2.15 working?

    i just tried updating 2.30 to 3.41 debug and its bricked it

  9. #69
    Registered User MSPARKY83's Avatar
    Join Date
    Mar 2006
    Posts
    13
    Lol, try it, and then tell me if it bricked it.

    Make sure that it is 2.15 Debug firmware though.
    Last edited by MSPARKY83; 12-06-2010 at 01:09 AM

  10. #70
    Senior Member BwE's Avatar
    Join Date
    Apr 2010
    Posts
    709
    Quote Originally Posted by MSPARKY83 View Post
    Lol, try it, and then tell me if it bricked it.

    Make sure that it is 2.15 Debug firmware though.
    lol oki. going from 3.41 modified to 2.15 debug as we speak <3

    give me 5 minutes

    and.. fail, it doesn't even start to write. it just fails.

    here's the log:
    manufacturing updating start
    PackageName = /dev_usb000/PS3UPDAT.PUP
    settle polling interval success
    vflash is disabled...
    boot from nand flash...
    creating flash regions...
    create storage region: (region id = 2)
    format partition: (region_id = 2, CELL_FS_IOS:BUILTIN_FLSH1, CELL_FS_FAT)
    create storage region: (region id = 3)
    format partition: (region_id = 3, CELL_FS_IOS:BUILTIN_FLSH2, CELL_FS_FAT)
    create storage region: (region id = 4)
    format partition: (region_id = 4, CELL_FS_IOS:BUILTIN_FLSH3, CELL_FS_FAT)
    create storage region: (region id = 5)
    create storage region: (region id = 6)
    Initializing
    taking a while...
    start Updating Proccess
    Initialize elapsed time = 22 msec
    check UPL
    Check UPL elapsed time = 27 msec
    check Package Size
    get package size elapsed time = 8 msec
    start Updating Package
    Update packages num = 21
    Update packages total size = 100379340
    Update Package Revoke list
    read package revoke list package (576 bytes) elapsed = 2 msec
    update package revoke list elapsed = 107 msec
    Update Package Revoke list done(0x8002f000)
    Update Core OS Package
    read core os package (4976256 bytes) elapsed = 267 msec
    update core os package elapsed = 172 msec
    Update Core OS Package done(0x8002f14b)
    update package elapsed time = 548 msec
    Updating or Verifying failure 0x8002f14b
    UpMng.UpdatePackage() failure
    manufacturing updating FAILURE(0x8002f14b)
    Total Elapsed time = 1561 msec
    Last edited by BwE; 12-06-2010 at 01:13 AM

 

Sponsored Links
Page 7 of 9 FirstFirst ... 56789 LastLast
Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News