haber quien tiene un par de traductores, segun dicen el incremento de la velocidad en el xmb es muy alta todo el tema del scroll y al volver del sleep mode dicen que es muy rapido el primer loco que lo ha intalado ahora se pondra ha probar los juegos haber que tal, bueno ah lo que ivamos quien tiene un par para traducir
PSP_FlashROM.txt
This is the consideration of BOOSTER concerning the built-in FlashROM of PSP and danger. Structure PSP of PSP built-in flashROM has built in NANDflashROM of 32MBytes. Three areas of IPL, IDStorage and MASSstorage it has divided here. The program in order to start PSP has entered in the IPL area. When here is broken, it stops starting PSP. It seems that the individual information of OpenPSID, MAC address and serial number etc. is recorded in the IDStorage area. You do not know detailed structure. Is accessed the file which as 'flash0' and 'flash1' is housed in the MASSstorage area. The physics of ECC and BadBlock/it has logical conversion function, but the format differs from general SmartMedia. Logically there is the HDD image and compatibility of DOS/V, with FW1.50 the below-mentioned four pas - has divided into t Shaun. 24560KB: 'flash0: ' Area 4080KB: 'flash1: ' Area 1008KB: Whether the sky, it is used in something unclear 944KB: Whether the sky, it is used in something direct access to of built-in flashROM prohibition is stopped altogether from the program of vulnerability user mode of unclear PSP built-in flashROM. On the one hand, other than file operation, through the physical driver, all area can be read and written from the program of kernel mode. In addition, through the driver, operating the hardware directly, also being possible to access, easily to make starting impossible, it increases PSP. As for the method of returning PSP of starting impossible state as for the manufacturer it is the expectation which it has, but if, presently because it is not known in the general user, PSP which has become starting impossible does not do manufacturer repair or reforming structure it does not return. And, with FW1.00/1.50 from vulnerability of the firmware, the homemade mosquito on メモステ - the flannel mode program finishes being able to start normally. You know executing the program of origin obscurity easily how, dangerous behavior probably will be? It limits the homemade software which can be executed easily to user mode, when operation of kernel mode is necessary, the user installs explicitly, with is not that the environment which is said is very desirable in the user, probably will be? By the fact that the below-mentioned condition of the execution program cord/code is inspected, the FlashROM destructive virus can be quarantined is. 1. The attribute of module has become kernel mode. 2. It has linked to "the sceMScm_driver" library. 3. It has linked to "the LflashFatfmt" library. 4. It has "flash", "lflash" and "flashfat" keyword 5. The API of sceIoAssign/sceIoUnassign is linked. 6. Address of the NANDFlash hard register is loaded. The file which is necessary for the starting PSP and XMB has entered in danger flash0 of flash0 rewriting. You write the normal operation time and exchanging is not done. The starting PSP is started from the IPL program which is written on IPL block, but it is necessary to be the file of flash0 and the version which has compatibility. The file which is stated inside pspcnf_tbl.txt and pspbtcnf.txt and pspbtcnf.txt inside flash0 having been even, there is a correct registry file in flash1 or, when the other file which is anew compilation possible, is necessary for the starting XMB in the plate has been even everything it can start. Unless either one among these condition is even one, it does not start PSP. Furthermore also the file which is stated in pspbtcnf_game.txt is necessary in execution of メモステプログラム. Unless it starts to here, it cannot move the homemade program. Verification still is, but Custom Firmware Dark Alex - The proof of concept use you obtain, there is no file which is necessary for registry and XMB and it is thought that also the て can start the return program. The case where at time devhook it starts from PSP built-in Flash this technology is diverted. Appreciation to Dark Alex! Usually, flash0 being to be mounted with lead/read mode, being written in and being protected, but when it re-mounts from kernel mode, entry becomes possible. Because as for flash0 the normal operation time it is read-only, if even the file which is necessary for starting it is guaranteed and the て is, it is less crowded and consumes the territory and it is thought that it is all right, to the last it is presumption, but. In FW1.50, 'flash0: ' The being less crowded area is 9280KBytes. When the font and the table of FW2.71 are installed in one for devhook0.46.0000, it is less crowded and the area becomes 4,624KBytes. The registry file and the other setting file etc. having entered in danger flash1 of flash1 rewriting, you write frequently even the normal operation time and substitute. Because flash1 is divided to another per t Shaun from flash0, cutting electric source while the accessing flash1, there are no times when flash0 is broken. But, when there is no registry file which is flash1 has been broken, it becomes a state where it cannot draw up anew, with FW1.50 over again it stops starting initialization and restart. As the circumstance which falls to this state, 1. File system with such as the power source stopping/deciding which is in the midst of writing in was broken. 2. Writing the other file at the time of registry file deletion, it was less crowded and the area became insufficient. 3. The file system was destroyed intentionally. 3 Tsugas it is thought mainly. With FW1.50 the other file of flash1 is deleted registry - at the time of initializing, and/or フォ - the mat in order not to do, becoming starting impossible is verification end even with method of 2. When flash1 is handled, you must pay attention to existence of the registry file and guaranty of the being less crowded area sufficiently. To write the registry file which on flash1 is rather frequently because it substitutes, the behavior where you do not use the power switch while the operating PSP and pulls out the electric battery and the AC cord/code and the hit it can point power source is dangerous. Furthermore, when the FlashROM device is put in write protection state, it does not start PSP. 'flash1: at time of FW1.50 initialization ' The being less crowded area is 3808KBytes.
FAQ
Notice and the report on the basis of etc. of BBS, it tried designating part as FAQ type. 2006.7. Q. It installs to built-in FlashROM being not to be dangerous? A. It is dangerous. Concerning the trouble which you can suppose it is it is experimented, but with the worst case there is a possibility PSP stopping starting. "flash0: "Compared to" flash1: "One degree of risk is low, is, but" flash1: You verify that it is the condition PSP stopping starting "with state. This is not the problem which is limited to devhook. After recognizing these risks, it is necessary to utilize. As for the one which cannot do the preparedness, until sufficiently it is operated is verified the person who refrained from use is good, probably will be. When FW2.60/2.71 is used with Q.devhook, the file inside メモステ is broken. A1. " Lash1: When "to FW2.60/2.71 is started when the setting file is not installed, the る thing where the below-mentioned file destructive condition occurs with USB connection and suspention after the web browser using of XMB is verified. ¥dh¥271¥flash1¥net¥http¥auth.dat: First allocation unit is invalid. ¥dh¥271¥flash1¥net¥http¥cookie.dat: Size of entry invalidity ¥PSP¥SYSTEM¥BROWSER¥historyi.dat: Because as for cross link especially cross link there is a possibility of destroying the other file in other allocation unit, at the time of the メモステ use to which the important file enters, we recommend that you do not use under the above-mentioned conditions. "flash1: When "the setting file is installed, this trouble does not occur. The above-mentioned error occurs as for メモステ, WindowsPC connecting by way of USB, "chkdsk.exe [ drive: ] You can verify error in /F "command/you can restore. It is thought that with the latent bug of A2.devhook0.45.0000, the occasionally file is broken. Bug was corrected with devhook0.46.0000, but it is lack of confirmation concerning the presence of trouble. Q.PSP freezes when choice character set Korean (949). A.It seems to be deadlock when open "kd/resource/cp949_table.dat". kd/resource must be installed in internal 'flash0: ' For Korean (949). Q. With the mass memory stick of part, XMB of devhook after the starting, when UMD is started, is frozen after the blackout. A1. There is a possibility of problem of memory allotment when restarting. When memory address is changed with preload address option, perhaps it can start. A2. As clearly cause at present is unclear. Feeding back the log of Kprintf, it cooperates to debugging or, please abandon. Installing Q.FW2.60/2.71, it does not start. A. The FW installer of attachment is part not yet correspondence in 2.60/2.71. Using the other tool, and the like it is necessary to extract reboot.bin.It extracts reboot.bin in the below-mentioned manner. 1. Loadexec.prx is decoded. (It becomes the ELF format) 2. The data after offset 0x3200 of loadexec.prx which it decodes is quarried out. 3. The file which it quarries out (the first decodes "- PSP") again. 0.43 At release point in time, GTA LCS product UMD and the decrypter software which correspond to PSP and GTA Exploit of FW2.60 are other way necessary in the decoding of reboot.bin. When it returns to XMB from the HOME key of Q.GAME, it freezes. When being operational with A1.333MHz, there are times when it occurs. When it operates with 222MHz, there are times when it stops occurring. As the restriction of A2.devhook, regrettable there is a case which reboot it is not possible. When memory address is changed with preload address option, perhaps it can start. If even then useless, please turn off power e.g., the electric battery is pulled out with. With A1.FW2.00/2.50 which cannot start UMD/ISO and the like above Q.FW version, when from the FEP menu, "UMD VERSION" - "2.xx to 2.00" is selected, the version cord/code on UMD is downgraded to 2.00. In case of FW1.50 jointly using, other loader such as MPHGL, it starts. As for the cryptographic key of time before A2.2.50 and after the 2.60 because it differs, as for the file which is encoded with 2.60 keys with FW of 2.50 or less being not to be able to load, the one which be as new as possible it starts with FW is good, is. With Q.FW2.50 at the time of CLOCK=333MHz, with Wifi connection it becomes error. It is not the problem of A.devhook, PSP itself above 223MHz as for Wifi connection seems like the specification, prohibition. When wlan.prx is replaced to the file of FW2.00, it operates due to latent bug, but originally for operation prohibition, it becomes the over specifications. The damage accumulates to PSP, when it is worst, being to be danger which is broken we do not recommend. The Q.MS lamp becoming, keeps lighting up ISO (UMD) becomes access impossible. A. Cause is not recognized well, but such as after the USB connection after MS is cut off, UMD-ISO are times when it becomes lead/read impossible. When with HOME + TRG-L and HOME + TRG-R ISO is changed, UMD and MS are done one time EJECT, there are times when it returns. The ISO image which Q.RIP is done does not start. With A1.FW1.50 in the route directory the sign cord/code is necessary in UMDDATA.BIN and PVD. You write the sign cord/code to the ISO file with umdsign.exe, or up-to-date UMDGEN (
http://www.umdgen.com) with you can write by the fact that ISO is constructed. With FW2.50 there is no sign cord/code, it seems that operates. It cannot load plain kernel on A2.UMD prx. Case the PRX file is replaced to the decoding file in the one for other loader, the original prx file you reset. When FW2.00/2.50 was started with Q.devhook, it stopped returning to the origin. A. Returning from suspention/resumption, game starting and the game to XMB, devhook continues to be permanently stationed. Power switchThe long pushing (sliding) being able to point, when it turns off one time power, it returns to the origin. Q. When one time devhook is started, it becomes not be able to start devhook launcher. A.devhook launcher 0.44 is not yet correspondence in the starting from FW2.00/2.50. When modifying setting, one time power is turned off or, installing reboot.bin of FW1.50, when rebooting pushing LTRG+RTRG+UP, after returning to built-in Flash once, the recovery moving て. The firmware rise data does not start in Q.devhook working condition. A. " Spcnf_tbl.txt "with setting, the starting updater is prohibited. Present devhook the hook has not done NAND driver level. Being to be equal to suicide behavior, you will stop. Whether or not with OS on devhook, by the fact that the wallpaper is modified, OS on MS it can distinguish at the glance, we recommend that the sea urchin it does. The starting menu "of reboot XMB" other than does not operate with Q.launcher. A. There is no various restrictions in the starting menu. Reboot XMB: With all modes yes reboot UMD: FW1.50 (flash)/with only FW1.50 yes load run UMD: 1.50 (Flash) With, MPHGL of dwvhook starting being completed: 1.50 (Flash) Only yes RunUMD: 1.50 (Flash) Only ISO is not recognized above yes Q.FW2.00 to NOUMD. A.NOUMD is FW1.50 exclusive use. Above FW2.00 doing the setting of NOUMD, automatic, it is modified to ANYUMD. Above FW2.00 the insertion of suitable UMD is needed. There is ISO which is not started with NOUMD in Q.FW1.50. Because A1.ANYUMD compatibility is higher, please try ANYUMD. As for UMD after A2.FW1.50, with FW1.50 there are also some which are not started. ISO of Q.Demo Disc Vol.2 does not start. A.ANYUMD corresponds to only the GAME disk. Because of the disk which includes the both of UMD GAME and UMD Video it cannot start Demo Disc Vol.2. It does not operate with PSP of Q.FW1.00. FW1.00 became not yet correspondence from A.V0.40. Because it cannot load 1.50 loadexec.prx on FW1.00, it cannot use. Please use V0.3x, or wait for corresponding release. Q. The launcher uses, the づ leprosy A. The source of the launcher is open. Please make those which you yourself are easy to use. Q. How doing, you use the compressed ISO file? A1.CSO (compression ISO), ISO image compression/can be developed with ciso.exe of attachment. A2. Because the tool which from the other volunteer it is easy to use with GUI is offered, you use that. Q. To change the plural ISO files? With XMB which is started from A.devhook, HOME with + TRG-L/HOME + TRG-R it changes to the following file inside the same directory. MPHGL cannot be started directly from Q.launcher. A1.MPHGL does not operate being to be FW1.50 exclusive use above FW2.00. It seems that it starts turning to A2.LAN switch ON. Because MPHGL is for FW1.50, after FW2.00 it does not move, (necessity is thought is not) with.
quien tenia un par
![[flipa]](/images/smilies/nuevos2/flipando.gif "flipando")
![[+risas]](/images/smilies/nuevos/risa_ani3.gif "más risas")
![[tadoramo]](/images/smilies/adora.gif "Adorando")
![[pos eso]](/images/smilies/nuevos2/pimp.gif "pescador?")
![[jaja]](/images/smilies/nuevos2/otrasonrisa.gif "otra sonrisa")
![[qmparto]](/images/smilies/net_quemeparto.gif "Que me parto!")
![[poraki]](/images/smilies/nuevos/dedos.gif "por aquí!")
![[beer]](/images/smilies/nuevos2/brindando.gif "brindis")
