|
|
#31 |
|
Member
![]() Join Date: Oct 2011
Posts: 708
Likes: 393
Liked 709 Times in 276 Posts
Mentioned: 115 Post(s)
Tagged: 0 Thread(s)
|
hold on a sec, just read my edit from last post
![]() i had a similar problem with you when i downgraded my slim, i used jaicrab's self and i ended up softbricking it. you need to check the dump inside your console with preloader. edit: or you could go back to jfw, but it's better if you give a shot at 3.55
__________________
"Whoever has ears, let them hear."
|
|
|
|
|
|
#32 |
|
Member
![]() Join Date: Jan 2011
Posts: 223
Likes: 3
Liked 7 Times in 6 Posts
Mentioned: 24 Post(s)
Tagged: 0 Thread(s)
|
i dont know how to check it with the preloader . . .or better what is a preloader i am a little confused . . .
|
|
|
|
|
|
#33 |
|
Member
![]() Join Date: Oct 2011
Posts: 708
Likes: 393
Liked 709 Times in 276 Posts
Mentioned: 115 Post(s)
Tagged: 0 Thread(s)
|
@sewershark
preloader is the jaicrab tool to backup and restore flashes. just set advanced.cfg to backup your NOR, put the lv2diag.self that came with advanced.cfg and start the console. oh, and make sure you set in the cfg to shutdown and not reset. and watchout for the restore option, leave it disabled , only enable the backup option (Backuprflash.bin).
after that, check it with HxD, which is an hex editor, in the points i've said to check
__________________
"Whoever has ears, let them hear."
|
|
|
|
|
|
#34 |
|
Member
![]() Join Date: Jan 2011
Posts: 223
Likes: 3
Liked 7 Times in 6 Posts
Mentioned: 24 Post(s)
Tagged: 0 Thread(s)
|
ok i can do all of that except the editing with the hex editor ,can you come back to me to this thread tomorrow?
|
|
|
|
|
|
#35 | |
|
Member
![]() Join Date: Oct 2011
Posts: 708
Likes: 393
Liked 709 Times in 276 Posts
Mentioned: 115 Post(s)
Tagged: 0 Thread(s)
|
__________________
"Whoever has ears, let them hear."
|
|
|
|
|
|
|
#36 |
|
Member
![]() Join Date: Jan 2011
Posts: 223
Likes: 3
Liked 7 Times in 6 Posts
Mentioned: 24 Post(s)
Tagged: 0 Thread(s)
|
|
|
|
|
|
|
#37 | |
|
Member
![]() Join Date: Oct 2011
Posts: 708
Likes: 393
Liked 709 Times in 276 Posts
Mentioned: 115 Post(s)
Tagged: 0 Thread(s)
|
__________________
"Whoever has ears, let them hear."
|
|
|
|
|
|
|
#38 | |
|
Member
![]() Join Date: Jan 2011
Posts: 149
Likes: 228
Liked 104 Times in 57 Posts
Mentioned: 39 Post(s)
Tagged: 0 Thread(s)
|
__________________
Co-developer of XMB Manager Plus - One of the few and maybe even the only open collaboration project on the PS3 Scene without any drama.
|
|
|
|
|
|
|
#39 | ||
|
Member
![]() Join Date: Jan 2011
Posts: 223
Likes: 3
Liked 7 Times in 6 Posts
Mentioned: 24 Post(s)
Tagged: 0 Thread(s)
|
i don't know anything about ros0 and 1,can you explain this ?anyway i still have the log of the patcher (rflash_patche.exe) and the flasher (egea,advance.cfg) that were used to try making the downgrade here is a copy of them ******************************* * JaiCraB 2012 * * http://jaicrab.blogspot.com * * jaicrab @gmail.com * ******************************* Main: Version 3.1 Main: Running main base! Main: Opening config file...OK Main: Analyzing configuration... Restore rflash: Opening device for backup... Nand model. OK! Restore rflash: Opening /dev_usb000/rflash.bin file backup...OK Restore rflash: Dump size 16MB Restore rflash: Starting rflash restore only sectors differents...COMPLETED! Main: Shutdowning! and rflash_patch.txt: Designed for the Demonhades.org community It is your responsibility!! Get info and minimal check... Size: 0x1000000 Model:Nand model trvk_prg Offset 0x51800 trvk_pkg Offset 0x53800 ros0 Offset 0x80010 ros1 Offset 0x780010 ros0 version: 356.000 (0x1a) ros1 version: 355.000 (0x18) metldr version: old model Creating rflash_new.bin...OK *** ** * * ****** *** *** * * ** ** * * * * * ** * * * ** * ** ** * **** * * ** * * * * * * ** ** * * * * * ** * * * * ** *** * * *** ** *** *** * * ** ** FINISH!. New rflash was created It is your responsibility restore this rflash_new.bin!! You can cause your system does not turn on. In that case, the only way to recover is with a physical flasher. Press key to close. both say that the process had gone through that is exactly what i also thought ,but when you make the dumb of the 256mb it wont work with rflash_patch.exe ,so i told that to demonhades thread (that i will link here) about this,i told them that my ps3 have 256nand,they confirmed that i still should choose option 1(first 16mb of nand) and not 2 (all of the nand) here is the line of the advance.cfg #Backup "rflash" to "/dev_usb000/Backuprflash.bin" # 0 = Disabled # 1 = 16MB Nor models and first 16MB from NAND models. # 2 = 16MB Nor models and 256MB from NAND models. ;1 <----- must be 1 and not 2 according to demonhades support link: this is the page where it tell them about the 256mb nand http://www.demonhades.org/foro/viewt...=6556&start=75 you can switch pages from 1 to the last to see my comments there,replys are in spanish i find the better way to use chrome that have a build in transaltor to understand them i still have all of the dumbs but the problem is that i am afraid that they wont be compatible with the actual state of the ps3 as it might be modified with the flashing(s) we did last night severla times what do you think : (creating flash regions... create storage region: (region id = 2) format partition: (region_id = 2, CELL_FS_IOS:BUILTIN_FLSH1, CELL_FS_FAT) create storage region: (region id = 3) format partition: (region_id = 3, CELL_FS_IOS:BUILTIN_FLSH2, CELL_FS_FAT) create storage region: (region id = 4) format partition: (region_id = 4, CELL_FS_IOS:BUILTIN_FLSH3, CELL_FS_FAT) create storage region: (region id = 5) create storage region: (region id = 6) i have 5 dumbs backup Backupflash1.bin size:204,544Kb Backupflash2.bin size:16.384Kb Backupflash3.bin size:512kb Backupflash.bin the one with 1 selected in advance.cfg size:16.384Kb Backupflash.bin the one with 2 selected in advance.cfg size:262,144Kb witch one should i flash and do you think i really should flash this way? i went to that channel in the past . . . no one really have that much to say there . . . i want to add another thing ,when i placed the lv2 self and the rogero pup the first time it bricked i realized that i kept the pup with original name and did not rename in to PS3UPDAT.PUP as anyone should have done . . . my mistake here because i spent to much time on this thing and i god really tired at then end and forgot about that . . but the 3-4 time when i tried to recover that the pup was renamed correctly . . . i wrote this just to let you assist me better if there is anything we can do about the actual state of the console also notice how in the link of the forum they choose a special lv2 self hosted on mediafire as somebody else have choosed a wrong generic one let me know and thanks for your support Last edited by sewershark; 05-17-2012 at 05:38 AM. |
||
|
|
|
|
|
#40 |
|
Member
![]() Join Date: Oct 2011
Posts: 708
Likes: 393
Liked 709 Times in 276 Posts
Mentioned: 115 Post(s)
Tagged: 0 Thread(s)
|
well, there's something here that's NOT correct, and that's the offsets in NAND flash, which is the one
@sewershark
has. Now correct me if i'm wrong, but i've NEVER seen ros0 and ros1 on 0x80000 and 0x780000, but instead on 0xC0000 and 0x7C0000, and that happens in BOTH NAND AND NOR. if SOMEHOW the team
at demonhades has managed to switch offsets with their jfw, then i have NO idea of what could be causing this. Like i said, your best option would be to either talk to the guys or join EFNET on irc, channel #ps3downgrade , although i'm not sure if it's possible they will help, but they'll certainly give their best to do so ![]() DO NOT FLASH ANYTHING UNTIL YOU'RE TOLD TO DO SO!!!
__________________
"Whoever has ears, let them hear."
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|