The above video goes away if you are a member and logged in, so log in now!
|
| |
Would you like to get all the new info from PSX-Scene in your email each day?
| |
|
-
about cfw and 3.55 –
01-09-2011,08:32 PM
So, patched (poke added) lv2 from 3,41 runs fine in custom 3.41
but patched same way lv2 from 3.55 result in brick
3.41 cfw was applied to normal system, 3.55 to 3.41 cfw (maybe smth messed up with poke call durring update?)
any idea what additional checks can be there ?
-
01-09-2011,08:39 PM

Originally Posted by
netkas
So, patched (poke added) lv2 from 3,41 runs fine in custom 3.41
but patched same way lv2 from 3.55 result in brick
3.41 cfw was applied to normal system, 3.55 to 3.41 cfw (maybe smth messed up with poke call durring update?)
any idea what additional checks can be there ?
Wow can you rephrase this. The sentences are hard to follow XD
EDIT: You patch a 3.41 kernel, put it in 3.41 pup, and it worked. I got that. But did you:
Put a patched 3.41 kernel in a 3.55 pup
or
Put a patched 3.55 kernel in a 3.55 pup
if the second one, did you use the same patch as 3.41? Because the point in the kernel to patch changes with each version. Not only the point, but if the structure of the code was changed, then the patch would change too.
-
01-09-2011,08:42 PM

Originally Posted by
Slynk
Wow can you rephrase this. The sentences are hard to follow XD
I know right?

Originally Posted by
netkas
So, patched (poke added) lv2 from 3,41 runs fine in custom 3.41
but patched same way lv2 from 3.55 result in brick
3.41 cfw was applied to normal system, 3.55 to 3.41 cfw (maybe smth messed up with poke call durring update?)
any idea what additional checks can be there ?
So.. you patched the poke call into a custom 3.41 lv2 (It worked)
You did the same with 3.55 and got a brick? I'm guessing I caught the gist..
-
01-09-2011,09:35 PM
yes, I figured now what's wrong with 3.55 lv2, segment wasnt encrypted after deflating
the hope is back
(not mine ps3 was broken but its still sad)
Last edited by netkas; 01-09-2011 at 10:07 PM.
-
01-09-2011,10:10 PM

Originally Posted by
netkas
yes, I figured now what's wrong with 3.55 lv2, segment wasnt encrypted after deflating
the hope is back
(not mine ps3 was broken but its still sad)
You broke someone else's ps3 doing that? Hahah. Hopefully it was worth it.
-
01-09-2011,10:16 PM
Netkas, by patching lv2 and your machine (or someone else's) bricking, you have no option to get it back right??? no Lv2 no Service mode, this sucks :S
Time to do a recovery menu on the ps3 on lv1 or something...
-
01-09-2011,10:16 PM

Originally Posted by
moose123
You broke someone else's ps3 doing that? Hahah. Hopefully it was worth it.
not me borked it, mine lv2 self for 3.41 worked fine.
-
01-09-2011,10:19 PM

Originally Posted by
Pockets69
Netkas, by patching lv2 and your machine (or someone else's) bricking, you have no option to get it back right??? no Lv2 no Service mode, this sucks :S
Time to do a recovery menu on the ps3 on lv1 or something...
well, with nor/nand flashing and eprom editing u can get it back, not easy tho
-
01-09-2011,10:24 PM
Yeah involves soldering, and the soldering points on this machine are tiny as shit, i guess we should have thought about a recovery menu on the ps3 long ago, beofre we start messing with these CFW, good luck to you netkas hope you succeed bud
-
01-09-2011,10:25 PM

Originally Posted by
netkas
not me borked it, mine lv2 self for 3.41 worked fine.
So you already have a Jailbroken 3.41 firmware with the poke syscall? :o
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|