|
|
#71 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,301
Likes: 1,129
Liked 640 Times in 525 Posts
Mentioned: 269 Post(s)
Tagged: 0 Thread(s)
|
i'm a little confused what happend here..all 3 dumps is 1 console? or 2 consoles?
goodluck on fixing it tho..
Last edited by haz367; 06-03-2012 at 10:10 AM. |
|
|
|
|
|
#72 |
|
Apprentice
![]() Join Date: Apr 2012
Posts: 17
Likes: 1
Liked 1 Time in 1 Post
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
lol
i just have one ps3, version cech-2004A if those good flashes i have, in the backups folder, are from other consoles, i don't know how i made them. i only used my bad one, and pro hacks modified one. I tried to plug the hdd directly to my ps3, and pressed the power button for a long time, it's still bricked. Now i'll try to reconnect the clip with the chip. And i don't want others people dumps to flash mine, i only wanted one to compare with my bad one, so i could fix it if possible. haz367, what i meant with using a 001000 swaped bytes .bin, is that i tried to flash the bios with a good dump, but the version with reverted bytes. ps3 wiki dev says that E3 makes a dump, with the bytes reversed (words appear like "htsi" (this), i think it's something about big and little endian). So i used flow rebuilder to swap the bytes, as they said in ps3 wiki dev. But those doesn't work. I have to use reversed bytes dumps, or else downgrade isn't possible. And believe me, it isn't impossible to repair bad dumps. It's just incredibly hard, i don't have the knowledge in programming that is needed to do this, but maybe there's someone who does. Meanwhile, i just have to keep trying, because i still believe the clip is well connected to the chip. as i said, i added some foam and tape so it keeps nicely fitted. If it wasn't, how was i able to do a good dump, even if it was a wrong dump i used to flash the bios, after the brick, and before the 2nd dump (the successful one). But i'll try it anyway. |
|
|
|
|
|
#73 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,301
Likes: 1,129
Liked 640 Times in 525 Posts
Mentioned: 269 Post(s)
Tagged: 0 Thread(s)
|
lol
![]() my bad there, was thinking it tho..cech2004a being your console.. ok..right..u have 3 dumps there, the second in the backup folder is a bad dump, missing per console info(alot) and if no way of recovering a full dump with the per console data of your cech2004a there's no way of fixing it..only if there's missing other info or with the help from another(bad)dump but with more/other per console info intact, so u must be very lucky to have this scenario ![]() it's clear now..i guess..u have 3 dumps there and used a dump from Pro.hack? if that file is the same as i have here, check the MD5 = MD5: 9d47f1c1f94384c388d8553ac9ec9d42...then u bricked it by using it as it's that one i posted previous from the wiki metldr/unhackable btw did u reclip the e3clip between dump/restoring? cuse if the second one = bad cech2004a dump is your first one made, that's for sure a bad clip connection, the other 2(good) ones so to speak have everything intact but it's not from cech2004a and i think other per console info also, the metldr file is complete on all 3 dumps, the second being ur original cech2004a dump, first one made = bad? if u then reclipped e3 and then instead flashed back the prohack dump with good e3clip connection this time, u may be screwed? as it's overwritten with other data, it must be? cuse those 2 dumps are complete = good e3 connection, very unlucky u are i think? i may be totally wrong here, its a mess tho ![]() could u do something, redump the bios and post it here..thx and for bytereversing...only if u work with Progskeet etc.. u'l need this option for E3, after installing,dumping the bkpps3.bin, only for verifying/wiki/values it u must byte reverse it so it reads ifi like "what" in ur example ![]() then if u sure it's correct u ALWAYS flash the original bkpps3.bin u made, not the swapped dumps, and if u use the manual E3 patches instead of "e3_downgrade.bin" it's the same thing, use the original bkpps3.bin u made with E3 restoring/flashing back a "byte reversed" e3 dump(fii/thaw) isn't gonna work, again use the original file Last edited by haz367; 06-03-2012 at 04:09 PM. |
|
|
|
|
|
#74 |
|
Apprentice
![]() Join Date: Apr 2012
Posts: 17
Likes: 1
Liked 1 Time in 1 Post
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
haz367, i bricked the console before flashing the bios with prohacks dumps, after that i tried all the stuff i could, including doing the other two backups, i didn't open the ps3 in between. I don't know if i have time today to do this, but as soon i reconnect the clip, and make a new flash dump, i'll post it here.
|
|
|
|
|
|
#75 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,301
Likes: 1,129
Liked 640 Times in 525 Posts
Mentioned: 269 Post(s)
Tagged: 0 Thread(s)
|
whoops
right..long story short..i just rechecked prohacks's dump and ur "complete" dumps in the backup folder
u never read the full topic there i'm afraid?! also info about what u can replace in a dump http://www.ps3hax.net/showthread.php?p=333405 although, the dump is still up, let's say this dump is crap/and indeed it's showing ros03.731/ros1 3.56_2, the values are unhackable console = Code:
0B CECH-25xx (JTP-001) with 3.56 from factory - datecode 1B E9 60 0E 92 2F5F0 2F 5B 2F 5B the weird thing, the second dump is the original u made?(cech2004a) with bad clip connection..must be , u didn't reclip but somehow the e3clip is connected good then as it restored?/made clean backups, only not ur data i'm afraidsomeone pls correct if wrong, my guess its perm-bricked after u bricked it first time, all u should have done is reclip and make backups, nothing else..no errase/restore modified dumps, then with some luck it didn't erase just like it didn't backup the bootloader_0 = 0 bytes very unlucky Last edited by haz367; 07-18-2012 at 07:45 PM. |
|
|
|
|
|
#76 |
|
Apprentice
![]() Join Date: Apr 2012
Posts: 17
Likes: 1
Liked 1 Time in 1 Post
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
well, i guess i have 2 options, first, use my ps3 as a huge paperweight, or... i can sell my 17 original games, and buy a used ps3. And then, try it again xD. At this point, i have both games and ps3 just laying around, so, selling the games won't do any harm. I can even keep this ps3, and use as spare parts for the other. I'll do it, just to say "fu*k you perm-brick"
![]() I didn't have the time to do it today, but i think i won't try to reconnect the clip, it's pointless... Now, any one wants a good game for 10 euros? xD Thanks a lot for your help and patience, i really apreciate it, in the future, i won't make the same mistakes ![]() edit i forgot to ask, if you still find a god dump from a cech 2004a, please post it here. I've been comparing my bad and my good dumps, there are 2 files that i need, cvtrm (root folder) and bootloader_0 (root folder), and then compare ros1 folder to see if i need anything. I could join (if possible) my bad dump good files, with a good dump good files missing from my bad one xD. It's worth a try, if i can get that dump. I've searched google, but so far, i've found none. Last edited by qUaK3R; 06-04-2012 at 04:16 PM. |
|
|
|
|
|
#77 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,301
Likes: 1,129
Liked 640 Times in 525 Posts
Mentioned: 269 Post(s)
Tagged: 0 Thread(s)
|
as a doorstop/paperweight..it's heavy enough hehe..no for real..it just sucks...and i've been there..but flashing back someone else dump wasn't a smart move..strange anyway cuse ur original dump is the bad one from the pack u posted right?
how it comes that this backup is incomplete(missing cvtrm/bootloader) and without reclipping its weird when u flashed that crapdump(prohacks?) and made 2 backups of it, both are complete, anyway the per console info isn't urs anymore cuse the modified dump has other per console info then urs/mine hence per console info...both are identical to that dump = brick if the e3 is connected 100% it has overwritten ur per console info( and i bed it was still there after first brick, the bad dump looked the same as my first brick wich afterall all per console info was still intact, even though it RLOD on me, but i stopped after the restore/reclipped/redumped and fixed it )i have a cech2004 complete backup for u, but it wont work yes u have empty bootloader_0(0bytes), missing cvtrm file and a corrupt ROS1 folder, if it only was the ROS being bad or let's say 2 corrupt dumps from same console, both have per console info intact, 1 has the cvtrm for example and the other one has enough other per console info..then the pro's like euss could fix it by replacing data/edit the dump with hexeditor reclipping atm is wasting time, as it seems fitted good, please dump it again just to be sure Last edited by haz367; 06-04-2012 at 05:25 PM. |
|
|
|
![]() |
| Bookmarks |
| Tags |
| #downgrade , #dualboot , #e3 , #help |
| Thread Tools | |
|
|