Sponsored Links

Sponsored Links

Page 2 of 9 FirstFirst 1234 ... LastLast
Results 11 to 20 of 81



  1. #11
    Registered User radialman's Avatar
    Join Date
    Jun 2010
    Posts
    26
    Sponsored Links

    cant hack it!!

    Sponsored Links
    I suppose with all the negativity and demands that have been coming his way lately "he just cant hack it" lol

  2. #12
    Registered User kasugano's Avatar
    Join Date
    Mar 2010
    Posts
    5
    Sponsored Links
    Sponsored Links
    The only thing that he left for us was sony removing the OtherOS!
    Last edited by kasugano; 07-13-2010 at 08:13 PM

  3. #13
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005
    Posts
    27,639
    Sponsored Links
    Sponsored Links
    Quote Originally Posted by xxkrizxx View Post
    what i think is best is to not release the exploit till the new games come out this year, like need for speed and twisted metal black and all those new games including killzone 3
    Normally that would ring true, but I don't believe these guys would release something that could easily be patched by Sony so hopefully it won't be an issue.

    Also, I wouldn't hold my breath for a PS3 hack/exploit release by September, as far as I know that is just what RichDevX is rumored to have told someone on IRC... it could be BS, false, a joke, etc. but if it's legit then great, of course!

    Update: According to Mathieulh, "nothing is planned on our end" so it appears RichDevX was either lying or joking on IRC... so much for his credibility, unless Mathieulh is lying like he does about using warez, eh?

    Time will tell for sure, but at least others who got access to GeoHot's private info and files are still working on hacking the PS3, which is really the important part as it means all hope is not lost even with GeoHot bailing from the scene.

  4. #14
    Contributor SiZMiK's Avatar
    Join Date
    Apr 2007
    Posts
    68
    He could have left us with something, at least 1 cfw that the devs could have continued. Yes he was clever enough to do what he did, but in the end all he did for us was leave us worse off. Thanks Geo.

  5. #15
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005
    Posts
    27,639

    Arrow

    Grojcig is also another guy who is starting some CELL related development work: twitter.com/grojcig

    From a few of the tweets:

    Another image i want you to look at :P [Register or Login to view links]

    Image shows the LS when the code in my last tweet executes [Register or Login to view links] Are the Stacks at the right place? Are the sizes correct?

    I'm not sure if i understood the Stack creation and managment for SPU correctly. Here's the code [Register or Login to view links]

    LS is something you can extremely abuse.There's no protection for stack overflows. Yesterday i managed to overflow it with recursive calls.
    Code:
    ###DATA SECTION###
    .data
    
    ##GLOBAL VARIABLE##
    #Alignment is _critical_ in SPU applications.
    #This aligns to a 16-byte (128-bit) boundary
    .align 4
    #This is the number
    number:
            .long 18
    
    .align 4
    output:
    	.ascii "The factorial of %d is %d\n\0"
    
    ##STACK OFFSETS##
    #Offset in the stack frame of the link register
    .equ LR_OFFSET, 16
    #Size of main's stack frame (back pointer + return address)
    .equ MAIN_FRAME_SIZE, 32
    #Size of factorial's stack frame (back pointer + return address + local variable)
    .equ FACT_FRAME_SIZE, 48
    #Offset in the factorial's stack frame of the local "num" variable
    .equ LCL_NUM_VALUE, 32
    
    
    ###CODE SECTION###
    .text
    
    ##MAIN ENTRY POINT
    .global main
    .type main,@function
    main:
    	#PROLOGUE#
    	stqd $lr, LR_OFFSET($sp)
    	stqd $sp, -MAIN_FRAME_SIZE($sp)
    	ai $sp, $sp, -MAIN_FRAME_SIZE
    
    	#FUNCTION BODY#
            #Load number as the first parameter (relative addressing)
            lqr $3, number
    
            #Call factorial
            brsl $lr, factorial
    
    	#Display Factorial
    	#Result is in register 3 - move it to register 5 (third parameter)
    	lr $5, $3
    	#Load output string into register 3 (first parameter)
    	ila $3, output
    	#Put original number in register 4 (second parameter)
    	lqr $4, number
    	#Call printf (this actually runs on the PPE)
    	brsl $lr, printf
    
    	#Load register 3 with a return value of 0
    	il $3, 0
    
    	#EPILOGUE#
    	ai $sp, $sp, MAIN_FRAME_SIZE
    	lqd $lr, LR_OFFSET($sp)
    	bi $lr
    
    ##FACTORIAL FUNCTION
    factorial:
            #PROLOGUE#
            #Before we set up our stack frame,
            #store link register in caller's frame
            stqd $lr, LR_OFFSET($sp)
            #Store back pointer before reserving the stack space
            stqd $sp, -FACT_FRAME_SIZE($sp)
            #Move stack pointer to reserve stack space
            ai $sp, $sp, -FACT_FRAME_SIZE
            #END PROLOGUE#
    
            #Save arg 1 in local variable space
            stqd $3, LCL_NUM_VALUE($sp)
            #Compare to 0, and store comparison in reg 4
            ceqi $4, $3, 0
            #Do we jump? (note that the "zero" we are comparing
            #to is the result of the above comparison)
            brnz $4, case_zero
    
    case_not_zero:
            #remove 1, and use it as the function argument
            ai $3, $3, -1
            #call factorial function (return value in reg 3)
            brsl $lr, factorial
            #Load in the value of the current number
            lqd $5, LCL_NUM_VALUE($sp)
            #multiply the last factorial answer with the current number
            #store the answer in register 3 (the return value register)
            mpyu $3, $3, $5
    
    		#EPILOGUE#
            #Restore previous stack frame
            ai $sp, $sp, FACT_FRAME_SIZE
            #Restore link register
            lqd $lr, LR_OFFSET($sp)
            #Return
            bi $lr
    
    case_zero:
            #Put 1 in reg 3 for the return value
            il $3, 1
    		
    	    ##EPILOGUE##
            #Restore previous stack frame
            ai $sp, $sp, FACT_FRAME_SIZE
            #Return
            bi $lr
    Props to dondolo for letting us know!
    Attached Thumbnails<br><br> Attached Thumbnails

    factorialstack.png   stackframesfactorial.png  
    Attached Files Attached Files

  6. #16
    Contributor chrykel's Avatar
    Join Date
    Jul 2008
    Posts
    88

    Angry

    good leave egohot! IT'S YOUR FAULT OTHER OS WAS TAKEN OUT ANYWAY! and everyone should just give up! i think the most we will see on ps3 is the exploits and nothing more... give up and update already!

  7. #17
    Senior Member itwong's Avatar
    Join Date
    Mar 2006
    Posts
    93

    Unhappy

    It's sad geohot has chosen to leave the ps3 and iphone scene. Well, it turns out planetbeing has managed to unlock and jailbreak the new iphone 4, iphone 3GS with new bootrom after all. Hence, not much of a big deal to the iphone scene. As for the ps3 scene, at least someone got ahold of geohot's metldr and lv2 dumps. Hopefully they make good use of them and do something for the community.

  8. #18
    Contributor semitope's Avatar
    Join Date
    Feb 2009
    Posts
    605
    what updates? he hasn't even put out anything =/ How's about you put out something, THEN give that excuse?

  9. #19
    Registered User xxLindenxx's Avatar
    Join Date
    Jul 2008
    Posts
    137
    after reading the comments, i can understand why he left. He still gave us a lot of stuff so even if he has a huuuuge ego, we probably should still thank or at least stop whining about him.

  10. #20
    Registered User Awayze's Avatar
    Join Date
    Jan 2010
    Posts
    21
    Quote Originally Posted by tripellex View Post
    All I have to say is, about freaking time. Lil wannabe pissant was all talk, all ego.
    It's people that are douches and caused him to stop hacking the iPhone. People who complain and moan are noobs who haven't followed him since 2007 and the first iPhone unlock.

 

Sponsored Links
Page 2 of 9 FirstFirst 1234 ... LastLast
Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News