why? they work fine, so why?
Printable View
why? they work fine, so why?
You mean custom gameboots work fine with it?
I've seen custom gameboots and backgrounds on a 2.8 TA-082, why wouldnt it work on a 2.71 TA-082? All I really want is backgrounds though.Zitat:
Zitat von Art
If it works fine, then why do you need X-Flash? Use that program.
And uh, you don't need to flash backgrounds you can just set them in the photo menu...
uhhmmm, lets see, for starters I have 2.71 NOT 2.8 and I have tried deviant flash for 2.8, it doesnt work on 2.71.Zitat:
Zitat von Kartoon
I was asking that you allow flashing of a gameboot/custom font etc...
Making X-Flash compatible with flashing to a 2.71 normal PSP. I am not requesting SE for a TA-082, but just want to be able to customize my firmware. It has nothing to do with the motherboard. Its just that no one has created an app for flashing a 2.71. Its like we are being ignored because now people are making things for 2.71SE and 2.8.
My request is that you allow a flashing of a gameboot to a 2.71TA-082 or not. There are absolutly NONE. There is always some problem that prevents a program from working. Even for PSPFiler. And the 2.71 SE gameboot/customizers are in 1.5 format...
Hey Art, there is an app made by 0okm that checks your mobo.
Ok, if the source is available for that it might change things.Zitat:
Hey Art, there is an app made by 0okm that checks your mobo.
The point is that if certain things are unsafe to do on TA-082, and a flashingZitat:
My request is that you allow a flashing of a gameboot to a 2.71TA-082 or not.
program runs on it, it might go fine for someone with 2.71, but someone else
with the wrong motherboard will use it and brick it, then it damages my rep
for their mistake.
I'm not mistaken your request for SE.. just pointing out that there must have
been a reason Dark_AleX wouldn't allow his flashers to run on TA-082s..
since otherwise he could have made it so you upgrade to SE from 2.71, and
not 1.50... but he didn't do that because he didn't want TA-082 users to run it.
.....he made it so you couldn't run it from 2.71 at all .. just so TA-082 users couldn't use it.
He didnt allow the flashers becasue a TA-082 cannot upgrade to 2.71 SE...It uses the 1.5 bootstrap. I dont think TA-082 can use that under normal circumstances.Zitat:
Zitat von Art
Yah! Now i can use X-Flash on SE-C!
ok, I had a look fo rthe gameboot flasher I was talking about (that didn't work on TA-082s), but instead found this:
http://forums.qj.net/f-psp-developme...-26-58670.html
It's said to work.
How do you start an app in 2.71? I assume an ordinary eboot doesn't start,
and there's some loader. .. I've heard of HEN, but have no idea what it is.
It needs to be a 1.0 eboot. There are some other aspects to is like the main module needs to be a user one...you can read up on it but I dont know what to tell you.Zitat:
Zitat von Art
That above program may work. It follows the above credentials.
Neither of them are a problem, although I thought an app had to be kernal mode to allow flash writing.
Maybe when I get some time, I will do a version locked to your PSP for you to test if you are game...
that way, it couldn't hurt anyone else.
In theory, it is very easy for me to support 2.71 from here..
I would only have to remove the checks for the SE versions for your PSP.
Actually, I will do that. There are a few secrets I haven't told anyone.
X-Flash already knows what time it is, so I can give an evaluation version an
expiry date, or make a special version work for only one day..
otherwise you'd have to keep setting your clock to that day to cheat it.
I just tried it. No Go:( . We just need a program specifically made for 2.71. That only works for 2.5 and 2.6. There are no programs specifically made for 2.71 so oh well. Thats the reason why it wont work.
-= Double Post =-
YAY. Hopefully it will work.Zitat:
Zitat von Art
I suppose I'll give that one away since it will be forgotten.
There is a special startup message for anyone who would still be using a
PSP with X-Flash fifteen (or was it ten?) years from now or later.
It could be discovered by spoofing the PSP system clock.
Art.
I will do it if i still have a psp by that time.Zitat:
Zitat von Art
You could just temporarily change the system clock to see it now ;)
Lol.. I was never going to tell anyone about it.
:p Lucky me. Got to see it before I got the boot in eLoader.Zitat:
Zitat von Art
If you download HEN-C, it gives you a brief explanation on how to program with HEN. It give some samples too.
This readme is from HEN-D.
- Revision A (22 september):
* Initial release
- Revision B (24 september):
* Some kernel prx's didn't load because the kernel tried to load them to user partition.
This problem affected devhook.prx and some other kernel prx's.
This problem has been fixed.
- Revision B with better binary loader in the tiff (25 september)
* Changed the binary loader to use the one from tiffsdk 1.1 that has better stability.
No changes on the core.
- Revision C (29 september):
* User mode static ELF's are now starting to work.
Tested with SNES TYL 0.3 (user mode version), PSPMaster and CPS2PSP 1.0 (user mode version).
Kernel mode static elf's are still not supported, they are a very odd case in 1.XX of kernel
code loaded to user memory.
Kernel Homebrew for 2.71 has to be written with a user main elf/prx that load kernel prx's.
Note that the homebrew must be in a true pbp, not kxploited!.
* User mode prx's could load other user mode prx's, but kernel mode prx's couldn't load user mode
prx's.
This is fixed.
* Patched the firmware to allow it to understand the old SFO format.
(avoiding the error of data is corrupted)
* Added a small win32 binary that will give you a hint about if a homebrew can work or not in
the current release. Note that this is only a hint.
- Revision D (25 November of ****ing year 2006)
* Fixed a bug in a patch bad done in a delay slot that caused some umd games not to work when HEN was
running (this issue was fixed in SE before)
* Fixed a bug in the loading of big user prx's, that affected a plain prx of socom2 umd, and some
homebrew prx's.
* Bypassed a crappy $ce protection that prevented the umd to be mounted if the application was run from
the memory stick
* Usb mass storage couldn't be loaded by homebrews in non-devhook version because semawm.prx is sign checked.
HEN now applies the algorithm to reverse the sign check, letting this and the rest of firmware
modules to be loaded by a homebrew.
* Added a SDK for HEN/SE.
Is it really 2016?
Go easy on this PSP eh!
So it's ten years then.... like still using the original PSX in 2005.
Not that special.. it should have been fifteen yrs for those that hunted them down on eBay.
Like I used to be with old Amiga computers.
help I keep getting the boot sayin psp parental control error.
Says try to disable parental control
I tried xflash 16G and SE-C
It says disable parental lock...Zitat:
Zitat von tuta
So disable parental lock! :Argh:
Thanks Art for the update, much obliged :tup:
Seeing as how fw2.80 has flash0 writing access, will an X-Flash program be released for it? I'm asking because I think Deviant Flash has stopped being released for fw2.80. :Argh:
i have been reading this thread..skimming through the pages but i still cannot understand what it is that the xflash do to the psp am on 2.71 SE-C ..can anyone give me a quick summary of wat xflash is ? thanks in advance
it edits your psp
like you know the game boot the noise thing you can edit that and the background etc
The front page comments become less intellegent for every release.
I'm not sure I can even understand what the flamers are on about.
There is mention of an error that I can't understand, and everything
seems fine to me, so if anyone else has a problem, please let me know
(and describe it better). I think it was another person new to X-Flash
who didn't know you can move sideways.
I think some dialogue will be needed in the next release to show people
that sideways movement selects other relative options.
Art.
Ok, I am not saying that I hate X-Flash(I used to love it to pieces) but it bricked my PSP. I am not saying it will brick everyone elses because it was my bad. I am thinking it was a bad gameboot because when I tried to add another, it failed and it didnt work.
So, i made it to return to the normal one but i got no sound at all at the gameboot. I was confused so i went to the #15 one, and went over until I saw Reset or something, so i clicked it and I thought it was good until something failed and it quit. Then, when I turned my PSP on, it had a blue screen with french words or something. It rebooted and kept doing that over and over.
LUCKILY(thankya dark alex) i had recovery mode(i was at 2.71 SE-B'') and got my PSP back.
I really do like your program and wish it the best of luck...but I cannot risk my little buddy lol.
If anyone would know why it would do this, please say why...
Out of space would be my best bet.
When you try to write a file that doesn't fit, and it fails,
the space that the partial file uses may not be relinquished because the file was never closed.
So then when you try to restore the original gameboot there may not be room left for that either.
I wouldn't have thought this would be the case until I started experimenting with a UMD ripper.
If you pull the UMD out before the rip is finished, the space
of the partial file remains consumed, but the MS appears to be empty.
None of these problems occured with 1.50 because nobody would ever consume the extra space on flash0
EVERY program that writes to flash has a chance to brick your PSP, it has nothing to do with Art or X-Flash. Plus, that sounds like your fault completely.Zitat:
Zitat von landon
I know it was my fault. I said...
. I am not saying it will brick everyone elses because it was my bad
I know that every flash program can brick your psp, i am not a noob. I just didnt know what i did wrong. I think that X-Flash is a great program and will always be the top of the homebrew flashing scene but I am not going to use it for my PSP's sake. I know, the program is 99% safe but I am usually that 1% :) . good luck art and dont take it that I dont like your program or blame it for my brick. It was my fault.
No worries, you asked for an explianation, and that's the best I can think of.
I haven't been game to flash anything larger than the POP gameboot mysef,
and that's only when there are no other options set that consume flash0 space.
dont worry, just a picky person :p
Sorry to ask, but what is POP stand for?
Good luck though. I wish you the best of luck in your programming and I hope you suceed in it...well, suceed even more I should say ^_^
Bye.
pop = prince of persia
ahhh. ok, thankyou. is that...the blood one?
probly...
I don't use it permanently, but the current size limitation for gameboots is
set to the exact size of that POP (blood & claw) gameboot because it is very popular.
Oddly enough, my nameplate doesn't show up when I set it with X-Flash. Works fine when I manually pop it in with PSPFiler though. Any idea what's up with it?
EDIT: I'm running SE-C, if it matters. The function didn't work in SE-B either. Think it might be because I left the file with a lowercase extension? Either way I'll leave the image, just in case.
Unrelated, but I'm stealing your nameplate :p