Go Back  
Reply
 
Thread Tools
Old 06-19-2012   #1
jackkiej
Member
 
Join Date: Oct 2010
Posts: 59
Likes: 1
Liked 3 Times in 3 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
ps3 downgrading error

Hello when i want to downgrade, USB on the far right, formatted on FAT32, e3 flasher all switches down,
with the Lv2diag.self and PS3UPDAT.pup from this thread: http://www.ps3hax.net/showthread.php?t=30815

i get this error:

Code:
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 = 78 msec
check UPL
Check UPL elapsed time = 56 msec
check Package Size
get package size elapsed time = 16 msec
start Updating Package
Update packages num = 28
Update packages total size = 163945171
Update Package Revoke list
read package revoke list package (576 bytes) elapsed = 2 msec
update package revoke list elapsed = 188 msec
Update Package Revoke list done(0x8002f000)
Update Core OS Package
read core os package (5212160 bytes) elapsed = 558 msec
update core os package elapsed = 51572 msec
Update Core OS Package done(0x8002f000)
Update VSH Package
sys_memory_container_create() success(id = 0xc0effffe)
Update VSH's package : 1/22
read vsh package (1870 bytes) elapsed = 3 msec
decrypt and verify vsh package elapsed = 45 msec
write vsh package elapsed = 113 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 32 msec
Update VSH's package : 2/22
read vsh package (1986317 bytes) elapsed = 215 msec
decrypt and verify vsh package elapsed = 154 msec
write vsh package elapsed = 146 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 129 msec
Update VSH's package : 3/22
read vsh package (4827124 bytes) elapsed = 520 msec
decrypt and verify vsh package elapsed = 314 msec
write vsh package elapsed = 236 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 276 msec
Update VSH's package : 4/22
read vsh package (4184462 bytes) elapsed = 451 msec
decrypt and verify vsh package elapsed = 277 msec
write vsh package elapsed = 454 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 283 msec
Update VSH's package : 5/22
read vsh package (3217207 bytes) elapsed = 354 msec
decrypt and verify vsh package elapsed = 238 msec
write vsh package elapsed = 551 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 273 msec
Update VSH's package : 6/22
read vsh package (25344 bytes) elapsed = 17 msec
decrypt and verify vsh package elapsed = 46 msec
write vsh package elapsed = 55 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 33 msec
Update VSH's package : 7/22
read vsh package (7317217 bytes) elapsed = 796 msec
decrypt and verify vsh package elapsed = 383 msec
write vsh package elapsed = 1006 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 366 msec
Update VSH's package : 8/22
read vsh package (10385664 bytes) elapsed = 1125 msec
decrypt and verify vsh package elapsed = 288 msec
write vsh package elapsed = 919 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 412 msec
Update VSH's package : 9/22
read vsh package (10266880 bytes) elapsed = 1112 msec
decrypt and verify vsh package elapsed = 293 msec
write vsh package elapsed = 1365 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 430 msec
Update VSH's package : 10/22
read vsh package (10195968 bytes) elapsed = 1108 msec
decrypt and verify vsh package elapsed = 278 msec
write vsh package elapsed = 427 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 399 msec
Update VSH's package : 11/22
read vsh package (10366208 bytes) elapsed = 1129 msec
decrypt and verify vsh package elapsed = 299 msec
write vsh package elapsed = 1512 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 452 msec
Update VSH's package : 12/22
read vsh package (10026496 bytes) elapsed = 1092 msec
decrypt and verify vsh package elapsed = 284 msec
write vsh package elapsed = 937 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 430 msec
Update VSH's package : 13/22
read vsh package (9574912 bytes) elapsed = 1050 msec
decrypt and verify vsh package elapsed = 358 msec
write vsh package elapsed = 1576 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 563 msec
Update VSH's package : 14/22
read vsh package (9217536 bytes) elapsed = 1011 msec
decrypt and verify vsh package elapsed = 439 msec
write vsh package elapsed = 1924 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 457 msec
Update VSH's package : 15/22
read vsh package (7992576 bytes) elapsed = 880 msec
decrypt and verify vsh package elapsed = 385 msec
write vsh package elapsed = 2209 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 447 msec
Update VSH's package : 16/22
read vsh package (8982224 bytes) elapsed = 987 msec
decrypt and verify vsh package elapsed = 392 msec
write vsh package elapsed = 952 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 480 msec
Update VSH's package : 17/22
read vsh package (8765184 bytes) elapsed = 968 msec
decrypt and verify vsh package elapsed = 354 msec
write vsh package elapsed = 2579 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 580 msec
Update VSH's package : 18/22
read vsh package (9576960 bytes) elapsed = 1056 msec
decrypt and verify vsh package elapsed = 297 msec
write vsh package elapsed = 1114 msec
Update VSH Package done(0x8002f057)
update package elapsed time = 95780 msec
Updating or Verifying failure 0x8002f057
UpMng.UpdatePackage() failure
manufacturing updating FAILURE(0x8002f057)
Total Elapsed time = 110506 msec

Last edited by jackkiej; 07-02-2012 at 09:40 AM.
jackkiej is offline   Reply With Quote
Old 06-26-2012   #2
alex-07
Member
 
alex-07's Avatar
 
Join Date: Jan 2012
Posts: 58
Likes: 20
Liked 23 Times in 17 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Originally Posted by jackkiej View Post
Hello when i want to downgrade, USB on the far right, formatted on FAT32, e3 flasher all switches down,
with the Lv2diag.self and PS3UPDAT.pup from this thread: http://www.ps3hax.net/showthread.php?t=30815

i get this error:


manufacturing updating start
PackageName = /dev_usb000/PS3UPDAT.PUP
settle polling interval success
vflash is enabled...
creating system regions...
..
write vsh package elapsed = 2579 msec
flush_cache(0x100000000000001)
flush_cache() SUCCESS
compare vsh package elapsed = 580 msec
Update VSH's package : 18/22
read vsh package (9576960 bytes) elapsed = 1056 msec
decrypt and verify vsh package elapsed = 297 msec
write vsh package elapsed = 1114 msec
Update VSH Package done(0x8002f057)
update package elapsed time = 95780 msec
Updating or Verifying failure 0x8002f057
UpMng.UpdatePackage() failure
manufacturing updating FAILURE(0x8002f057)
Total Elapsed time = 110506 msec
Update error 0x8002F057 Error with installing Firmware update in service mode: "Bul-ray Disc Player Revoke done(0x8002f057). Updating or Verifying failure 0x8002f057. UpMng.UpdatePackage() failure. manufacturing updating FAILURE(0x8002f057)" // caused by downgrading and using normal lv2_diag.self and not a noBD firmware (using the jaicrab lv2_diag.self as workaround will cause one ROS to be empty and can result in RLOD/GLOD/RSOD).

solution: use on usb root: rogero_v31 + lv2diag.self (365kB)

if you like to get live help, join the chat ps3downgrade or chat ps3downgrade

use better this for chat channels
alex-07 is offline   Reply With Quote
Old 06-26-2012   #3
haz367
Senior Member
 
Join Date: Dec 2010
Posts: 2,034
Likes: 1,034
Liked 580 Times in 471 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
Post

Originally Posted by alex-07 View Post
using the jaicrab lv2_diag.self[/B][/COLOR] as workaround will cause one ROS to be empty and can result in RLOD/GLOD/RSOD).

solution: use on usb root: rogero_v31 + lv2diag.self (365kB)
hmm, this is weird, i always use the same set/normal self+rogero 3.1 and always 1 empty ROS folder after downgrade, re-install recovery and fixed

somehow this is weird cuse it should occur only with jaicrab noBD patched self? never used that one, all downgrades where with working blu-ray either connected or disconnected but not broken, i never seen a RLOD/GLOD because of it, i must be duymp cuse i don't get, with normal selfs why is the ROS empty

MD5: 099f33a7967f99e91c07e870fd78b3db

http://www.ps3devwiki.com/wiki/Downg...ice_Mode_SELFs



edit: @playerkp420
thx for confirming the same issue, that's the "like it" for btw..not the empty ros

i had removed older pm's and cannot exactly remember what jhax78 told me about it whoops.....atleast something with a bug somewhere in the downgrade, not sure about the file1/enter Lv2diag.self being the bug

either, cuse i know ur using the "default" E3 downgrade like me right? either way the manual/Progskeet patches are different and perhaps safer in use, or its because of not doing the step2-restore bios before step3-e3_downgrade.bin/bkpps3.bin, i haven't used the manual patched way, although its a step less and perhaps safer/better patches?!

either way after downgrade, one must dump again and check it..always and if my memory not fails on me, jhax also told me to fix it either recovery(works fine) or doing 2xFSM rogero3.1?? not tested..not sure

the first one i bricked/downgraded with empty ros folder doing installs and stuff, nothing happend, only after dumping i noticed...never a RLOD/GLOD/RSOD tho...i'm testing teensy atm wish me luck...

Last edited by haz367; 06-26-2012 at 06:52 PM. Reason: ros
haz367 is offline   Reply With Quote
Old 06-26-2012   #4
playerkp420
Senior Member
 
Join Date: Dec 2011
Posts: 4,416
Likes: 958
Liked 1,532 Times in 1,103 Posts
Mentioned: 785 Post(s)
Tagged: 0 Thread(s)
Originally Posted by haz367 View Post
hmm, this is weird, i always use the same set/normal self+rogero 3.1 and always 1 empty ROS folder after downgrade, re-install recovery and fixed

somehow this is weird cuse it should occur only with jaicrab noBD patched self? never used that one, all downgrades where with working blu-ray either connected or disconnected but not broken, i never seen a RLOD/GLOD because of it, i must be duymp cuse i don't get, with normal selfs why is the ROS empty

MD5: 099f33a7967f99e91c07e870fd78b3db

http://www.ps3devwiki.com/wiki/Downg...ice_Mode_SELFs
I always get an empty ros folder too. Doesn't matter which self I use.

Edit - @haz367 - Yeah, I don't know why the ros folder is always empty. I thought it had something to do with Rogero cfw. I always just do dehashing with the empty ros, and both ros folders are filled again, once I'm on OFW3.55.
I never seen any RLOD/GLOD/RSOD either.
__________________
HOW TO DOWNGRADE W/E3 FLASHER TO ANY OFW/CFW
Nor model PS3 downgrade service in U.S.A. if you don't want to do it yourself
For downgrade help join irc at effnet-Just enter name and channel is #ps3downgrade

Last edited by playerkp420; 06-26-2012 at 11:10 PM.
playerkp420 is online now   Reply With Quote
Likes: (1)
Old 06-28-2012   #5
jackkiej
Member
 
Join Date: Oct 2010
Posts: 59
Likes: 1
Liked 3 Times in 3 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
it was already fixed, if you guys want to know
jackkiej is offline   Reply With Quote
Old 07-02-2012   #6
jackkiej
Member
 
Join Date: Oct 2010
Posts: 59
Likes: 1
Liked 3 Times in 3 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Originally Posted by haz367 View Post
hmm, this is weird, i always use the same set/normal self+rogero 3.1 and always 1 empty ROS folder after downgrade, re-install recovery and fixed

somehow this is weird cuse it should occur only with jaicrab noBD patched self? never used that one, all downgrades where with working blu-ray either connected or disconnected but not broken, i never seen a RLOD/GLOD because of it, i must be duymp cuse i don't get, with normal selfs why is the ROS empty

MD5: 099f33a7967f99e91c07e870fd78b3db

http://www.ps3devwiki.com/wiki/Downg...ice_Mode_SELFs



edit: @playerkp420
thx for confirming the same issue, that's the "like it" for btw..not the empty ros

i had removed older pm's and cannot exactly remember what jhax78 told me about it whoops.....atleast something with a bug somewhere in the downgrade, not sure about the file1/enter Lv2diag.self being the bug

either, cuse i know ur using the "default" E3 downgrade like me right? either way the manual/Progskeet patches are different and perhaps safer in use, or its because of not doing the step2-restore bios before step3-e3_downgrade.bin/bkpps3.bin, i haven't used the manual patched way, although its a step less and perhaps safer/better patches?!

either way after downgrade, one must dump again and check it..always and if my memory not fails on me, jhax also told me to fix it either recovery(works fine) or doing 2xFSM rogero3.1?? not tested..not sure

the first one i bricked/downgraded with empty ros folder doing installs and stuff, nothing happend, only after dumping i noticed...never a RLOD/GLOD/RSOD tho...i'm testing teensy atm wish me luck...
lol, i had the empty ros folder this time too, i looked at the statistics of my backup and i thought this can't be true.. i saw that the ros1 folder was empty for me. i am now dehashing and i will look if the ros folder is not empty after this.
and about the manual patching (flash fun mode), this is much safer then with the e3_downgrade.bin, for me with the one key downgrade 9 of 10 times fails for me, and flash fun mode works 9 in 10 times for me :P.
jackkiej is offline   Reply With Quote
Reply

Bookmarks

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



PS3Hax.net is Copyright © 2010-2013.
Use of this site is governed by our Terms of Use and Privacy Policy. All Trademarks and images are owned by their respected owners.
Posts and links are subject to each author on this forum and are no way affiliated with the operations and/or opinions of ps3hax.net
All times are GMT -5. The time now is 08:31 PM.