You can view the page at http://psgroove.com/content.php?531-...e-to-Dev_Flash
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
You can view the page at http://psgroove.com/content.php?531-...e-to-Dev_Flash
interesting indeed to bad the source is labeled as DH..... wonder what will come of this
would be really kool to have a way to switch between dev_flash's to for example run a 3.55 cfw an ofw 3.15 (otheros) so we wouldnt have to downgrade each time or some thing
Where is the new dev_Alejandro directory located? is this loaded from the flash chip, usb or hdd? If it is an extra directory added to the flash memory, how are we suppose to have an extra copy of this directory without running out of space? I'm guessing the chip has a limited amount of space close to what the size of the PS3 update packages are.
We already have the ability to mount dev_flash from another directory. The old apps load a custom dev_flash from a usb device. I don't see any major advantage to loading it directly from the flash chip while also keeping the original dev_flash on the chip, because as stated earlier, you will probably run into limited storage issues because you basically have two firmwares stored on the chip which was designed with enough space for a single firmware.
Your probably better off using one of the earlier released apps that allow loading custom dev_flash from the HDD, where you won't have such a storage limitation. That will be as good as it gets until someone finds a way to write over the original dev_flash directory on the firmware chip.
So to make it short, this is not nearly as exciting as the title suggests. We're still not writing to dev_flash, your just redirecting it to somewhere else that you have access to write files too. Which we have been able to do ever since the usb firmware loader app was released.
Alejandro hmm its sounds like Dark_Alex ...![]()
Well, excuse me if I'm missing something obvious but doesn't having write access to /dev/flash make it possible to change the behavior of the machine from boot? rather than from when a loader is executed from gameos or w/e...
@SwordOfWar: My understanding of this less-than-awesome translation, is that this app allows /dev_flash to be mounted to /dev_Alejandro, and then we can write to the /dev_flash *via* /dev_Alejandro.
But, this translation leaves a lot to the imagination.
I understood it the same way as craig0r after throw the source-spanish-page through google-translation:
I think that after reboot the" /dev_Alejandro mirror" overwrites the original /dev_flash.
(kinda like raid)...That means that any changes made to "dev_Alejandro" will be applied
to dev_flash
But I'm not 100% sure...
@hideki yes so this could allow cfw so you don't have to jailbreak
and @SwordOfWar yes its just redirecting dev_flash to /dev_Alejandro but it is permanent unlike the other apps where you had to jailbreak and then run the usb loader so if you modify it, it is like that even in retail mode.
| « Previous Thread | Next Thread » |