|
|
#31 |
|
Apprentice
Join Date: Feb 2008
Posts: 7
Likes: 0
Liked 0 Times in 0 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
I heard there is new method for this you should downgrade to 3.15 debug firmware first then update to 3.15 retail and then you can update to 3.41retail and there you go ))
|
|
|
|
|
|
#32 |
|
Senior Member
![]() Join Date: Jun 2009
Posts: 5,125
Likes: 1,880
Liked 1,789 Times in 1,170 Posts
Mentioned: 220 Post(s)
Tagged: 0 Thread(s)
|
1) u cant update from debug 3.15 to 3.15 retail
2) this is not the place to talk about best way to down grade use the search button and find the proper page to talk about the best way to downgrde and u get your . 3) keep to the topic of this page 4) if there was a way to jailbreak any firmmware other than 3.41 it would be front headline page on the site . not on some 100% fake website trying to act like there the real jailbreak team . |
|
|
|
|
|
#33 |
|
Member
![]() Join Date: Sep 2007
Location: Brazil
Posts: 171
Likes: 12
Liked 8 Times in 7 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
I believe that the 3.41 FW used isn't the best. I was having the "Blinking green" issue with a FAT PS3 and all I did was to use 3.21 to downgrade it instead of 3.41.. For Slims, I think it would be nicer if you guys tried to use a different version going from 3.50 to 3.30 I guess. The 3.41'CFW' isn't known for it's compatibility.
|
|
|
|
|
|
#34 | |
|
Senior Member
![]() Join Date: Jan 2008
Location: Lisbon, Portugal
Posts: 6,681
Likes: 2,087
Liked 2,449 Times in 1,389 Posts
Mentioned: 138 Post(s)
Tagged: 0 Thread(s)
|
__________________
<eussNL> judge: ´so why did you torrent 5 million AVI of women moaning´ <eussNL> <TizzyT> i dont judge if it sounds good i listen |
|
|
|
|
|
|
#35 |
|
Member
![]() Join Date: Jul 2009
Posts: 70
Likes: 1
Liked 3 Times in 3 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
Reply
Got a 160GB yesterday, here's the log
Click here to see full text
manufacturing updating start
PackageName = /dev_usb000/PS3UPDAT.PUP settle polling interval success vflash is enabled... creating system regions... create storage region: (region id = 1) create storage region: (region id = 2) format partition: (region_id = 2, CELL_FS_UTILITY:HDD0, CELL_FS_UFS) create storage region: (region id = 3) format partition: (region_id = 3, CELL_FS_UTILITY:HDD1, CELL_FS_FAT) creating system regions done. boot from nor flash... creating nor flash regions... create storage region: (region id = 2) create storage region: (region id = 3) creating flash regions... create storage region: (region id = 1) 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) Initializing taking a while... start Updating Proccess Initialize elapsed time = 58 msec check UPL Check UPL elapsed time = 71 msec check Package Size get package size elapsed time = 22 msec start Updating Package Update packages num = 30 Update packages total size = 162260220 Update Package Revoke list read package revoke list package (576 bytes) elapsed = 22 msec update package revoke list elapsed = 191 msec Update Package Revoke list done(0x8002f000) Update Core OS Package read core os package (5182047 bytes) elapsed = 326 msec update core os package elapsed = 263 msec Update Core OS Package done(0x8002f14b) update package elapsed time = 803 msec Updating or Verifying failure 0x8002f14b UpMng.UpdatePackage() failure manufacturing updating FAILURE(0x8002f14b) Total Elapsed time = 14474 msec 0x8002f14b is the error, left it for half an hour on blinking and no go...
__________________
![]() |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|