Yeah, harleyg said there is a way back.
The big problem will come if people don't like to use the new shell. Will there be a way back?
Yeah, harleyg said there is a way back.
Then I'm gonna try it when it's released.
I might give it a shot, so long as there are no reports of brickage. As I said, writing to flash is tricky business. Fonts and some customized firmware aren't so bad, but replacing the entire XMB with a new Shell just begs for trouble.
I hope it does work because it will pave the way for other XMB replacements, maybe someday, even Linux.
Those prxs could go straight to the memory stick, like they should, and it'd function all the same. He's not replacing the XMB at all, he's just using a method similar, if not the same, as the customized firmware thing to autoboot it.Originally Posted by F9zDark
Besides, just because he says it replaces the XMB doesn't mean it does. I could say the sky is red, but that doesn't make it so.
If you can boot right back into the XMB with the push of a button, then he's replaced nothing.
He's not overwriting the XMB. He's not replacing it. He's just autobooting an eboot that draws its files from flash0. Like the devhook thing. If you flash the devhook files to flash0, are you necessarily replacing your 1.5 firmware? No. They're just there to load the devhooked firmware faster. That isn't necessary for this homebrew 0x89 as if it fits in flash1, then there's no way its size is big enough to see a long load.I might give it a shot, so long as there are no reports of brickage. As I said, writing to flash is tricky business. Fonts and some customized firmware aren't so bad, but replacing the entire XMB with a new Shell just begs for trouble.
I hope it does work because it will pave the way for other XMB replacements, maybe someday, even Linux.
I got you word from the Lead Developer and Project Leader's mouth about it replacing the XMB, so I'd think he means that he is indeed replacing the XMB.
He said that anyone can 'go back' to 1.5 if they wish. This indicates to me that he means there is indeed an uninstall feature.
If you read the 0x89 forums you will see clearly that he intends on replacing the XMB with his shell. That it won't be a 'customized firmware' per se, but nearly an entire overhaul of the 1.5 firmware and XMB.
More proof from the same thread:
If the XMB was never replaced, then someone could just install the update and have 0x89 files left alone. But since it actually REPLACES the XMB, once an update is applied it will overwrite all of the files that 0x89 replaced with its own, with Sony Update files and may even resort with a brick.Rabbit: "Custom Firmware"s out today are really just very simple mods. 0x89 is a vastly superior and more complicated mod. Nothing is a custom firmware or a firmware replacement. 0x89 still needs a Sony firmware to work. What it's doing is removing the XMB (the menu system you're on when you quit to home or boot without a UMD), and replacing it with a better, custom-made one, which can be updated independently of the firmware so that features and improvements can be made to it without altering how programs behave. IE: homebrew won't need to be recompiled for a different firmware every time 0x89 gets an update. In fact, homebrew [probably] won't need to be recompiled at all with the 0x89 mod.
harleyg: Correct.
Atleast someone understands. Tongue
saggar: is there a possibility, that since 0x89 is on Flash, that someone could have it installed, then upgrade there psp firmware, and keep 0x89 on the flash?
harleyg: No.
So I think the evidence is quite clear (aside from the sentence "it will replace the Sony XMB") that the XMB is indeed being replaced by 0x89.
Whatever. You can't simply remove the XMB and use your own. The PSP doesn't work like that. The PSP is not something you just dump something on. It's not a big truck. It's a series of tubes.Originally Posted by F9zDark
I don't even know why I'm arguing over this as 0x89 will never be finished.
What the hell are you talking about? Flash contains files, which can be overwritten, deleted, or repaired with the right tools. If the XMB couldn't be removed or altered then flash wouldn't be as troublesome as it is.Originally Posted by smith1
The true Trojan.Bricker actually erased all the files in Flash0 (XMB files, PRXs, everything) leaving people with a $250 paper weight. Another example of this was back in the day when the PSP was in its infancy in the US and homebrew was first discovered, Sony put up a fake updater on their site (probably testing the feature site wise and the PSP's built in network update feature). Some wise folks over at PS2dev.org found it, installed it and were left with bricks, because the update wrote files to flash, but some weren't right or were corrupted.
If what was in the flash couldn't be altered, removed, or changed, then
1)We wouldn't have the option to update, since it would be impossible
2)We wouldn't have to worry about writing to flash, since we couldn't!
You really need to do some research man...
I just wish we could have some what of an idea, when this is going to be released. The whole idea behind this sounds really awsome =D
@smith1
many users here have told yo that it will repalce the XMB, and they have even given links....yet you still continue with saying that it will not replace it. Dude, get your facts straight, or shut up.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks