Page 5 of 12 FirstFirst 123456789 ... LastLast
Results 41 to 50 of 113

Thread: 1.50 Kernel Add-on for 3.71 M33 Released

                  
   
  1. #41

    Default

    DarthPaul aren't you going to finish helping me with Pandora, you just stopped answering my PM's about the msipl.

  2. #42
    DCEmu Legend DarthPaul's Avatar
    Join Date
    Apr 2006
    Location
    Puerto Rico
    Age
    35
    Posts
    2,734
    Rep Power
    90

    Default

    Oh yeah dude, lol let's not put this off-topic. I'll pm you, and tell you what happened.

  3. #43
    DCEmu Old Pro pt9087's Avatar
    Join Date
    Feb 2006
    Location
    England, Hull
    Age
    35
    Posts
    1,331
    Rep Power
    84

    Default

    There are alot of n00bie questions in here,

    Dont forget ladies most sepugins do not work in 3.71 M33, even with this +1.5 patch.

  4. #44
    DCEmu Old Pro mavsman4457's Avatar
    Join Date
    Mar 2006
    Location
    East Coast, USA
    Posts
    1,278
    Rep Power
    75

    Default

    Quote Originally Posted by pt9087 View Post
    There are alot of n00bie questions in here,
    Here comes another one: I am still a little bit scared to update from 3.40 OE to 3.71 M33. I've heard of a couple of stories of bricks and I don't want to deal with Pandora's battery or anything like that. Aside from downgrading from 2.00 to 1.50 and then updating to 3.40 OE I haven't messed with my flash at all. I've pretty much ignored all posts about Flash1, 2, and 3, and 0 so I don't know how I would have messed those up or even what they do. Do I have anything to worry about in updating to 3.71 M33 and what are the common causes of bricks when dealing with 3.71 M33?

  5. #45

    Default

    Quote Originally Posted by MicroNut View Post
    Warning: For those upgrading to 3.71M33 because it can use homebrew now.
    There is a possible BSOD Full Brick after using Recovery F1 formatter (Format flash1 and reset settings)
    Or by accessing "Themes" after an upgrade to 3.71M33 without Restoring System Defaults in the XMB first.
    So, basically, don't use the flash1 formatter from recovery, and make sure the first thing you do when booting into 3.71M33 is restore default settings ...

    That sound about right?

    By full brick ... can it be recovered using Pandora?

    Do we know WHY this bug has come about?

  6. #46
    DCEmu Newbie
    Join Date
    Oct 2007
    Posts
    1
    Rep Power
    0

    Default thanks for this

    thanks alot just to let you know you are all welcome to join us at a new forum now open feel free to pop in and take a look round

    its still in the works and has been only open for 24 hours but still feel free to take a look

    http://pspchatforum.freeforums.org/index.php

  7. #47

    Default

    I've encountered the BSOD bug, after I installed 3.71 i went right to themes (since it's a new update and all) and the BSOD came up. I pressed start (DONT PRESS CIRCLE) and it rebooted itself, then when I started it up again it went through system settings.

    So for any reason you guys encounter the BSOD, press Start and no Circle.

  8. #48
    PSP User psp411's Avatar
    Join Date
    Nov 2005
    Location
    t.dot
    Posts
    241
    Rep Power
    72

    Default

    Quote Originally Posted by SpooForBrains View Post

    By full brick ... can it be recovered using Pandora?
    Yea... pandora can fix it... i formatted my whole flash0 drive on my 'recovered by pandora' psp(took 5 min lol) and pandora still worked on it. I dont think the psp can rly do anything to itself that will render the pandora meathod useless

  9. #49
    DCEmu Legend DarthPaul's Avatar
    Join Date
    Apr 2006
    Location
    Puerto Rico
    Age
    35
    Posts
    2,734
    Rep Power
    90

    Default

    Quote Originally Posted by mavsman4457 View Post
    Here comes another one: I am still a little bit scared to update from 3.40 OE to 3.71 M33. I've heard of a couple of stories of bricks and I don't want to deal with Pandora's battery or anything like that. Aside from downgrading from 2.00 to 1.50 and then updating to 3.40 OE I haven't messed with my flash at all. I've pretty much ignored all posts about Flash1, 2, and 3, and 0 so I don't know how I would have messed those up or even what they do. Do I have anything to worry about in updating to 3.71 M33 and what are the common causes of bricks when dealing with 3.71 M33?
    Hmm, first of all, you can't upgrade from 3.40 OE to 3.71, you need 3.52 M33-4 to do it.

    The common causes, well, I don't think you should care about that. I've seen that you've been here since a long time ago, and you're on 3.40 OE, so you must know about all of this already, there's no need to worry for someone like you. The causes here, are the people that don't know what they're doing, or just people that are careless, and of course mistakes everyone make.

    So to be secure, I suggest that you put your PSP back to normal, like flashing the original Flash of your current firmware. Then install 3.52 M33 and then straight to 3.71 M33.

    I hope you upgrade, it's worth it, nothing to lose, a lot to earn. Also, more 3.71 users, more stuff that will come for it for sure. So... good luck.

  10. #50
    DCEmu Pro MicroNut's Avatar
    Join Date
    Aug 2005
    Location
    here or there
    Posts
    777
    Rep Power
    77

    Default

    Quote Originally Posted by SpooForBrains View Post
    So, basically, don't use the flash1 formatter from recovery, and make sure the first thing you do when booting into 3.71M33 is restore default settings ...

    That sound about right?

    By full brick ... can it be recovered using Pandora?

    Do we know WHY this bug has come about?
    Thats right.
    No recovery menu.

    I just finished using a special .image that was supposed correct any partition problems on the NAND.
    That didn't fix the problem either...

    Somehow, I remember this being a problem a long time ago with early cfw...
    maybe my brain playing tricks on me.

    Edit:
    I have been told its a problem with a corrupted F1
    Or Bad partitions on the NAND itself...
    I cant post the link to work log or the things I have tried here.
    First bricks being reported with this problem started on or about: 09/26/07
    Yes, it can be fixed by Pandora... just finished that dance and much more over the last few hours.

    Quote Originally Posted by legitnelite View Post
    So for any reason you guys encounter the BSOD, press Start and no Circle.
    Pressing start is easier than shutting down like I suggested.
    Good find.
    You may want to follow/read the rest of the thread if you want your F1 to work correctly... wallpaper, themes... etc...

Page 5 of 12 FirstFirst 123456789 ... LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •