DarthPaul aren't you going to finish helping me with Pandora, you just stopped answering my PM's about the msipl.
Printable View
DarthPaul aren't you going to finish helping me with Pandora, you just stopped answering my PM's about the msipl.
Oh yeah dude, lol let's not put this off-topic. I'll pm you, and tell you what happened.
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.
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?Quote:
Originally Posted by pt9087
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 ...Quote:
Originally Posted by MicroNut
That sound about right?
By full brick ... can it be recovered using Pandora?
Do we know WHY this bug has come about?
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
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.
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:D :cool:Quote:
Originally Posted by SpooForBrains
Hmm, first of all, you can't upgrade from 3.40 OE to 3.71, you need 3.52 M33-4 to do it. :)Quote:
Originally Posted by mavsman4457
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. ;)
Thats right.Quote:
Originally Posted by SpooForBrains
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.
Pressing start is easier than shutting down like I suggested.Quote:
Originally Posted by legitnelite
Good find.
You may want to follow/read the rest of the thread if you want your F1 to work correctly... wallpaper, themes... etc...
Guys when do you think the topmenu_plugin.RCO files will work on 3.71 M33, and with this kernal update will this let some of the plugins such as VSHAnalog work? When will POPS work?
I dont know but my guess is that 3.52 top_menus, as they are, probably will not ever work on 3.71M33Quote:
Originally Posted by CaptainMorgan4
becuase the format has changed so much.
The good news is that a few of the more popular themes already have been converted for use in 3.71M33
They are snap to install: Evolvexmb
And CXMB 2.5 makes them just a little more customizable:
CXMB 2.5 Tutorial for 3.71M33
I hope Popsloader is fixed becuase its a must have plug-in for me.
MicroNut remember the pure Silver and Gold icons that were released a couple months ago, how can I get those to work in 3.71 M33?
Captain you can convert them using the Sony's Custom Theme Creator and then copy the PTF file into PSP/THEME.
Oh, where is the PSP/THEME folder located at please?
well.... i tried it...didnt like 3.71 M33 and decided to go to 3.52...
bad news is...i ended up with a full brick...
ill suggest people that if they dont like 3.71 M33, and would like to go back to say..... 3.52 M33-4... you might as well not think about it ( unless you have pandora... )
i need to now make a pandora battery to fix mine...
good thing i have 2 backup psp's :)
Thanks for Everything,
PSPdemon
P.S. why i didnt like 3.71 M33 was because...
-UMD games took longer to load
-boot-up's took longer to load on xmb
-random crashing
-buggy theme's ( not really a big issue....just a little annoyance :p )
I don't understand if the plugins don't work and POPS doesn't work why is DA done with this 3.71 M33 Custom Firmware? Can anyone tell me if VSHAnalog works in 3.71 M33 now that we have the 1.5 kernal update. DarthPaul, question I have the topmenu_plugin.rco file for the Platnium icons I wish to install on 3.71 M33 when my PSP is fixed tomorrow, how do I convert it into the files I need to be able to get it to work on 3.71 M33?
In theory yes.Quote:
Originally Posted by CaptainMorgan4
But you really have to know how to make / remake the icons to begin with. :(
Unfortunately, its not as simple as extracting the old icons as importing them into the Sony app.
CorrectQuote:
Originally Posted by DarthPaul
The learning curve is a bit high imo...
at least for my tiny brain.
The Sony custom theme tool is listed on the front page of EvolvXMB's website.
The best English manual I could find is here: customthemeguide.zip
I am not using it.Quote:
Originally Posted by PSPdemon
No pops.
I am only testing it out on a spare psp.
Pandora is an awesome thing.
I had first seen my PSP brick on 3.71M33 on the 26th...
Only started reporting it here when homebrewers got on it with the 1.50 plug-in...
Thought it would be a good idea to warn people
And give myself something to do on a Sunday afternoon.
(testing, formating, flashing and re-flashing)
the problem is... people don't listen. I've always said to go to settings and reset to default after ANY update (including official ones). I thought after doing this just now(couldn't turn it on at all), that I had a brick but After removing the battery for a few seconds and putting it back, It turned on just fine. I reset default settings and have not seen a single bsod.
Also... everyone needs to get off of the damn kxploited programs already (2 seperate folders) And for the person who deleted the corrupt one... I sure hope you're new or you deserve a slap with a wet fish :). Anyway, install pspbrew on your computer and convert all of your kxploited crap to a 1.0 eboot. If you have a normal 1.5 PSP that you use as well as your CFW PSP, then run the kxploit patch on the 1.5 so it can use them too.
No *SINGLE* eboot that was made for 1.5 kernel has any kind of problems with this firmware. Nor does PSX or anything else.
Why do this? Like we need it, that's why the Hide Corrupt Icons option is on the Recovery Menu.:pQuote:
Originally Posted by urherenow
The problem with this is even if they do exactly as you say.Quote:
Originally Posted by urherenow
When they get to the BSOD Pressing O = Full Brick
Pulling the battery does nothing...
Pressing start button (which does not work for me)
or shutting down the PSP at the BSOD is the only workaround.
Then you have to go in and rebuild the F1 folders for themes and wallpapers to work.
The worst part of it is not knowing if your going to run into that problem until it happens
Then you have to be prepared to recover the NAND with Pandora.
Whats worse is that no matter how you delete or format F1 its always a BSOD and pressing O = Brick.
I agree with the rest of what you said.
As Grif once said:
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOO NOOOOOOOOOOOOHOHOHHHOHOOOOOOOOOOOOOOO
(I bricked it by accident for those that don't under stand that LOOONG "NO")
MicroNut if this process of converting the icons is complicated could you possibly make one for me and anyone else who wants them. I guess I'm making a request, I always use them and if I can have them I will go to 3.71 M33 (I love the new XMB features but with no platnium icons wasn't worth it to me) instead of staying at 3.52 M33. Do you know which ones I'm talking about, heres a link so your sure:
http://www.dcemu.co.uk/vbulletin/sho...light=platnium
If you would do this for me (I just need the Silver ones) I would greatly appreciate it.
Wow, sounds like more talk about people using custom themes/icons and bricking. Why not just use one of the SONY themes? They are not too bad.
Anyway, Thank you Dark_AleX, I have successfully upgraded 2 "classic" PSP's to this with no problems at all.
Looks like more people run into trouble with running themes. I once ran a theme on mine but figured, it was pointless since Sony was releasing a new firmware every 4 days, rendering the old theme useless. I think homebrew is kick ass but themes are totally a waste of time imo.
BTW, the POPS emulator works MUCH better than the others. FF7 seems to run smoother :), thanks DA and now that homebrew runs, there's no need for the POPs loader!
well, I never saw the BSOD at all during my update. I can only assume that it's because I had already reset default settings as soon as I did the 3.52 m33 (ie. my flash1 was all good to begin with).
*"Reset to Default settings" DOES delete your registry and all and rebuilds your F1 folders... that's the whole point of doing it*
Second... How many bricks have resulted on PSPs where somebody installed custom stuff directly to thier flash (themes or prxs or whatever)? It's always a good idea to put things back the way they were before doing something like this.
Now, the kxploit thing? Do it because some things that don't like running under 3.60+ cfw as a kxploit actually DOES run as a single eboot. Do the patch just once on your 1.5 and you don't have to do it again, and then you don't have any incompatibilities (at least not for a stupid reason such as kxploit)
I wish I could but I cannot.Quote:
Originally Posted by CaptainMorgan4
This is different than the Popstation Icons.
Unngh... I wouldn't be surprised if people were bricking because they were writing themes directly to the flash.Quote:
Originally Posted by urherenow
The discussion about behavior before the bricking and what in involved is clearly described in this thread and in other forums.
It has nothing to do with writing themes to the NAND.
I have not had one problem with 3.52M33-4
I can flash back and format the F1 at will with no problem.
I know what its for and
I know what *"Reset to Default settings" means.
I have a clean 3.52M33 to work from.
Its built from a known good "clean_part_fat.image" file... with the same results.
I have not had one problem with Themes in 3.71, wow...
I actually think the new theme system is a good idea on Sony's part..
With the exception of playing with the 3.71 reboot prx (well after I bricked and recovered it several times)
I never ever write anything to the NAND.
I have even been slammed for not practicing such a "noob" like operation.
I have been an advocate of not writing to the nand for a long time.
I could really care less about who uses kxploit and who doesn't.
wow how are so many people having issues? Anyway, I updated my PSP Phat succesfully, now running 3.71 M33 with 1.50 homebrew support, saves having to use Noobz 1.5 ELoader that they just recently released for the PSP Slim.
On another note, what causes all these bricks? Lack of following directions, or just bad luck?
From what Micronut is saying, it sounds like a genuine bug. I'm guessing that the layout of flash1 has been changed between 1.5 and 3.71 and that the interaction of the two can somehow lead to it becoming corrupt.
I was encountering some problems with the Applecor theme on 3.52 ... for some reason when I booted without a memory stick inserted it wouldn't load the XMB fully. So I downgraded to 1.5. After that I decided I might as well try 3.71m33. So my PSP was as close to stock as I could get.
Seems like going back to 1.5 and resetting to default settings before you even start might be a good idea for those looking to update. It may be an unnecessary step - maybe just unflashing any custom themes and resetting to defaults is enough, I'm not sure.
Anyone in the Hull area got a pandora ??? got a brick here :(
Wow, there are so many users reporting about bricking their psp.. now im in doubt if i will update my psp 3.52 M33-4 to this firmware?? it has a nice custom theme dusplay and the popsloader are more compaltible to psone games, i hope that i dont brick mine when updating it.:confused:
mine was my own fault it updated fine i messed with flash 0..Quote:
Originally Posted by kryst abegnalie
So far every brick report I've seen for 3.71M33 has involved people messing with flash0 - with the exception of the bug that Micronut reported, of which we have seen one corroboration so far.
Not that I'm implying that you're wrong Micronut, just to be clear. I'm just saying that the vast majority of bricks reported have been from people flashing stuff.
Just tested it out. Tested some homebrew, AFKIM v3 doesn't work. Anybody got AFKIM v3 working?
just worked out my skin after updating iam going to lose it again :( any converters ?
Think i'll wait till an easy all in one comes out. too many bricks and i aint made pandora/magicstick yet ...
ok... for the comment about too much difference between 1.5 flash1 and 3.71 flash1.
NOW I REMEMBER! When I first installed the 3.71CFW (even on my slim) That was the ONLY time I ever went somewhere else before resetting to default first. I looked at the themes and as soon as I went there, I got the BSOD, and hit O, and it reset fine.
Soooo... how many people here installed 3.71CFW and then installed the 1.50 patch immediately afterword? That might be the problem with some of the reported bricks.
INSTALL UP TO 3.52 M33-4 (if you haven't already)
INSTALL 3.71 M33
**RESET TO DEFAULT SETTINGS**
INSTALL 1.50 PATCH
I bet if you do it in that order you won't have any problems. Reset default settings while on 3.71 (without the patch) will sort out your flash1 BEFORE a brick.
I have AFKIM v3 working. Before the 1.50 kernel add-on was released. :pQuote:
Originally Posted by -Xandu-
Just use the 3.XX kernel version.
I did the following steps:
1)Install 3.52 M33-4
2)Install 3.71 M33
3)Install 1.50 add-on
4)Restarted PSP and restored factory defaults
5)The first config screen showed to me, but in the PSP name settings occured an internal error (800XXXX) and BSOD. Ooops...
6)I pressed O (I had Pandora Kit, so no fear of a brick), the PSP restarted.
7)The first config screen appeared again, so i configured anything including PSP name.
8)No bricks and my PSP remains more stable than 3.52 M33-4.
All the emulators and apps for 1.50 kernel worked fine. Umd, umd backups and 3.xx kernel apps too.
And my flash1 had some problem because if my PSP is shut down for much time it AWAYS become corrupt. It shows me BSOD and i press O... and everything returns ok.... it occurs for all FW and CFW.