Post: [3.60] important if not found yet!!!! Reply fast!
Options
04-24-2011, 01:47 AM
#1
Fuser's Hoe
Banned
If this has been found already please ignore
Ok so i was bored and everyone was complaining on how they couldnt get to recovery mode on the ps3 for 3.60... so i was screwing around and..... i got it. im on 3.60 and just did the turn off thing a lil different. if this has been found please tell me. if this has not been found then i will prove to you and show a video TUT on how to do it. I have a feeling this has been found. so please be easy on me. im not as perfect as the haters want me to be. so hate all you want but everyone will know that your not being the adult about it.
UPDATE-----
I CAN ALMOST TASTE THE DOWNGRADE!
ALMOST THERE!!!
The following 11 users say thank you to Fuser's Hoe for this useful post:
04-24-2011, 05:27 PM
#56
yoh2
You talkin to me?
Originally posted by 911
I thankyou for your support. i gtg for the day though. it's easter! 
---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------
I shit you not, this is no lie my friend. is wasnt a FULL downgrade is what you may be thinking. you wouldnt understand it but it is a half and half.
---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------
I shit you not, this is no lie my friend. is wasnt a FULL downgrade is what you may be thinking. you wouldnt understand it but it is a half and half.
People are confused, because they think you can get out of "factory service mode" on 3.60 but you can't. And yeah there are many people come so far with "downgrade" on 3.60 but you can't downgrade with any of this methods this is proof.
04-24-2011, 05:29 PM
#57
Fuser's Hoe
Banned
04-24-2011, 05:42 PM
#59
Fuser's Hoe
Banned
Originally posted by yoh2
Ok then tell me why u are first saying "just downgraded to 3.55" ... and now you trying to tell me this wasn't a FULL downgrade, well in my eyes if you were on 3.60 and now on 3.55 it IS a full downgrade....
You may think that is the only thing but actually the downgrade messes up your firmware until you upgraade. i got the homebrew though but i can only get a few to work. like comgenie and multiman. and lv2
---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------
100TH POST! HAHAHAH YAY! I GTG IT's EASTER!!!!!!!
04-24-2011, 05:53 PM
#61
bezeek
Guest
I fully believe this is feasible, and urge you not to give up. I almost posted once about some ideas I had in making this work, but was afraid of the flaming that would likely follow.
A couple suggestions I have to minimize the chance of errors: use small, slow, identical USB sticks, and to modify the sticks' filesystems via. hex editor, to ensure the data has precisely the same alignment on both sticks.
(Note: If one had the proper equipment, analysis of the data read process by hardware logging of the USB stick during the update would effectively identify the exact moment when sticks should be swapped. This would be done by piggybacking a USB debugger off the USB stick's hardware, probably with a quick soldering job and a *nix box.)
The one specific problem I see with this procedure is the fact that the PUPs are encrypted. Because of this, loading part of one PUP and the rest of another would be very likely to result in garbage that won't decrypt properly, if at all. However, it would be theoretically possible to generate padding such that the beginning part of the data on stick #2 matched the part of the data loaded from stick #1 before the swap.
These are just my two cents, and all I hope is that someone with more skill than myself can build off of them.
Good luck, and don't listen to the haters!
A couple suggestions I have to minimize the chance of errors: use small, slow, identical USB sticks, and to modify the sticks' filesystems via. hex editor, to ensure the data has precisely the same alignment on both sticks.
(Note: If one had the proper equipment, analysis of the data read process by hardware logging of the USB stick during the update would effectively identify the exact moment when sticks should be swapped. This would be done by piggybacking a USB debugger off the USB stick's hardware, probably with a quick soldering job and a *nix box.)
The one specific problem I see with this procedure is the fact that the PUPs are encrypted. Because of this, loading part of one PUP and the rest of another would be very likely to result in garbage that won't decrypt properly, if at all. However, it would be theoretically possible to generate padding such that the beginning part of the data on stick #2 matched the part of the data loaded from stick #1 before the swap.
These are just my two cents, and all I hope is that someone with more skill than myself can build off of them.
Good luck, and don't listen to the haters!
The following user thanked bezeek for this useful post:
04-24-2011, 07:04 PM
#62
Fuser's Hoe
Banned
Originally posted by bezeek
I fully believe this is feasible, and urge you not to give up. I almost posted once about some ideas I had in making this work, but was afraid of the flaming that would likely follow.
A couple suggestions I have to minimize the chance of errors: use small, slow, identical USB sticks, and to modify the sticks' filesystems via. hex editor, to ensure the data has precisely the same alignment on both sticks.
(Note: If one had the proper equipment, analysis of the data read process by hardware logging of the USB stick during the update would effectively identify the exact moment when sticks should be swapped. This would be done by piggybacking a USB debugger off the USB stick's hardware, probably with a quick soldering job and a *nix box.)
The one specific problem I see with this procedure is the fact that the PUPs are encrypted. Because of this, loading part of one PUP and the rest of another would be very likely to result in garbage that won't decrypt properly, if at all. However, it would be theoretically possible to generate padding such that the beginning part of the data on stick #2 matched the part of the data loaded from stick #1 before the swap.
These are just my two cents, and all I hope is that someone with more skill than myself can build off of them.
Good luck, and don't listen to the haters!
A couple suggestions I have to minimize the chance of errors: use small, slow, identical USB sticks, and to modify the sticks' filesystems via. hex editor, to ensure the data has precisely the same alignment on both sticks.
(Note: If one had the proper equipment, analysis of the data read process by hardware logging of the USB stick during the update would effectively identify the exact moment when sticks should be swapped. This would be done by piggybacking a USB debugger off the USB stick's hardware, probably with a quick soldering job and a *nix box.)
The one specific problem I see with this procedure is the fact that the PUPs are encrypted. Because of this, loading part of one PUP and the rest of another would be very likely to result in garbage that won't decrypt properly, if at all. However, it would be theoretically possible to generate padding such that the beginning part of the data on stick #2 matched the part of the data loaded from stick #1 before the swap.
These are just my two cents, and all I hope is that someone with more skill than myself can build off of them.
Good luck, and don't listen to the haters!
I thank you for the support and ideas. you make a great point and If your ideas work I will -without hesitation- give you a great amount of credit.
The following 3 users say thank you to Fuser's Hoe for this useful post:
The following user thanked sergyu2500 for this useful post:
04-24-2011, 10:44 PM
#64
dishguy06
Haxor!
Hornet's just a dumb 12 year old kid trolling you all haha. if it was THIS easy you'd think someone could have figured it out by now. it's been sometime since 3.56 and 3.60 came out....
if you have something, post a video proof of you doing it or else don't bother at all. Don't get peoples hopes up because this method is 100% tried and fails.
if you have something, post a video proof of you doing it or else don't bother at all. Don't get peoples hopes up because this method is 100% tried and fails.
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
