Results 1 to 20 of 20

Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.


Thread: Use the SDK to make jailbroken 1.1.4 apps?

  1. #1
    Default Use the SDK to make jailbroken 1.1.4 apps?
    Have any of you tried to make an app in the SDK, and then upload it into your jailbroken 1.1.4 iPhone/iPod and run it? I would think that sort of thing is possible.
    Last edited by avihappy; 2008-03-07 at 02:32 AM.

  2. #2
    My iPhone is a Part of Me
    Join Date
    Aug 2007
    Location
    Heart&[email protected], USA
    Posts
    583
    Thanks
    7
    Thanked 44 Times in 36 Posts

    awesome idea, thats what i was thinking, is it possible?
    i want the AIM app :I

  3. #3
    Thumbs down Fail!
    It does NOT work. When I build one of the sample apps, and ran it in the emulator, it worked. But then, I built the app and uploaded it to my jailbroken 1.1.4 iPod Touch, and it failed to run. It would just hang on load, not even the GUI came up. I had to delete it.

  4. #4
    Green Apple
    Join Date
    Feb 2008
    Location
    grand junction colorado
    Posts
    38
    Thanks
    12
    Thanked 3 Times in 3 Posts

    don't you have to pay 99 dollars to run it on iphone
    RY GUY!!!

  5. #5
    There's probably something that's missing in the iPhone or in the application that prevents it from running all the saw. What if you try a terminal application to see if it can be executed first. Also, what about putting an unofficial application onto the iPhones the legal way? Think it'll work when it comes out in June?

  6. #6
    1. Using the SDK to create apps to install with jailbreak is against the SDK agreement. Apple can take away your SDK.

    2. Running applications on the iPhone requires the $99 certificate, so no one can compile for the device yet. Well, at least I can't

    3. It will take a jailbreak sort of effort to crack the digital security certificates that Apple will be using to sign apps that are loaded through the store.
    Starlight Computer Wizardry
    Pocket-sized Development
    Follow me on twitter: @NetMage

  7. #7
    My iPhone is a Part of Me
    Join Date
    Aug 2007
    Location
    Heart&[email protected], USA
    Posts
    583
    Thanks
    7
    Thanked 44 Times in 36 Posts

    when are we going to get the AIM and the MS exchange? we will need to wait till june for the next update O_o?

  8. #8
    Quote Originally Posted by NetMage View Post
    1. Using the SDK to create apps to install with jailbreak is against the SDK agreement. Apple can take away your SDK.

    2. Running applications on the iPhone requires the $99 certificate, so no one can compile for the device yet. Well, at least I can't

    3. It will take a jailbreak sort of effort to crack the digital security certificates that Apple will be using to sign apps that are loaded through the store.
    Yea, I figured that there is some DRM on these apps. Oh well, I guess we may have to wait until June.

  9. #9
    When i compile one of the sample sdk apps and try to run it on my iphone it instantly crashes, so at first i thought maybe it's this drm stuff, but when i looked at the crash reporter log file i found this:

    Dyld Error Message:
    Symbol not found: _OBJC_CLASS_$_NSAutoreleasePool
    Referenced from: /Applications/skrot.app/skrot
    Expected in: /System/Library/Frameworks/Foundation.framework/Foundation

    It seems like the symbol names are different. Maybe they will change the frameworks in the 2.0 firmware to enable sdk apps.

  10. #10
    What about compiling the source from the demo apps in the existing toolchains?

    Ive not had much luck so far with references to missing files etc.
    Those that tried compiling with the SDK, did you compile for the emulator, or did you compile for the iPhone.. Watching the apple video its clear that compiling for the emulator is a different thing to the actual hardware, that may be part of the reason it doesnt work.
    Last edited by Pyrofer; 2008-03-07 at 02:39 PM.

  11. #11
    Quote Originally Posted by Tomer View Post
    when are we going to get the AIM and the MS exchange? we will need to wait till june for the next update O_o?
    that's a rhetorical question, right?

  12. #12
    Quote Originally Posted by roventskij View Post
    When i compile one of the sample sdk apps and try to run it on my iphone it instantly crashes, so at first i thought maybe it's this drm stuff, but when i looked at the crash reporter log file i found this:

    Dyld Error Message:
    Symbol not found: _OBJC_CLASS_
    Referenced from: /Applications/skrot.app/skrot
    Expected in: /System/Library/Frameworks/Foundation.framework/Foundation

    It seems like the symbol names are different. Maybe they will change the frameworks in the 2.0 firmware to enable sdk apps.
    Yeah, I figured commenting out the NSAutoreleasePool (bad idea, considering that NSAutoreleasePool helps release memory) line might help, but it turn out that they've change the name of almost everything.

    My question is, if I pay the $99 can I still use my iPod Touch for things or does it become a debug unit. Because I really want to program for the iPhone/iPod Touch in OpenGL and the emulator can't handle that.

  13. #13
    iPhoneaholic
    Join Date
    Sep 2007
    Location
    Australia
    Posts
    353
    Thanks
    3
    Thanked 48 Times in 38 Posts

    Quote Originally Posted by roventskij View Post
    When i compile one of the sample sdk apps and try to run it on my iphone it instantly crashes, so at first i thought maybe it's this drm stuff, but when i looked at the crash reporter log file i found this:

    Dyld Error Message:
    Symbol not found: _OBJC_CLASS_
    Referenced from: /Applications/skrot.app/skrot
    Expected in: /System/Library/Frameworks/Foundation.framework/Foundation

    It seems like the symbol names are different. Maybe they will change the frameworks in the 2.0 firmware to enable sdk apps.
    The 1.2 frameworks have to be installed on the iPhone. In other words it'll only work with 1.2 firmware. The firmware is being released to select developers as part of a beta program. Also, I would bet the 2.0 beta is locked still
    Last edited by imode; 2008-03-08 at 01:30 PM.

  14. #14
    The Aspen platform that's installed as part of the SDK includes a number of frameworks and libraries that are used to develop iPhone apps w/ Xcode. Not sure if they're the iPhone compatible versions or not but it might be a starting point.

    The essential problem with the apps not running is that the 1.2 FW frameworks it's using are not available. I scp'ed over the Aspen frameworks but to no avail (it accepted the QuartzCore ones and whatever but it wouldn't accept the Foundation.framework, which also screwed up some other apps).

    So that's all the progress I've made. Also, getting iPhone apps to run in the Aspen simulator doesn't seem to work either because the Aspen apps are compiled with a different platform configuration and are completely different from the UIKit Apps. The few apps that are available, MobileSafari and the like, have been compiled for AspenSimulator by Apple.

    Oh, and I'm also planning on buying the 1.2 beta (the $99 one) so I maybe able to get the apps to run on earlier firmwares by screwing with the frameworks, if that doesn't breach some sort of NDA or whatever.
    Last edited by Drakenza; 2008-03-08 at 05:37 AM. Reason: Forgot to mention one thing.


    Anshu Chimala
    Follow @anshuchimala on Twitter
    Visit http://www.airpoke.com, my latest project for iPhone/iPod touch.

  15. #15
    Quote Originally Posted by Drakenza View Post
    The Aspen platform that's installed as part of the SDK includes a number of frameworks and libraries that are used to develop iPhone apps w/ Xcode. Not sure if they're the iPhone compatible versions or not but it might be a starting point.

    The essential problem with the apps not running is that the 1.2 FW frameworks it's using are not available. I scp'ed over the Aspen frameworks but to no avail (it accepted the QuartzCore ones and whatever but it wouldn't accept the Foundation.framework, which also screwed up some other apps).

    So that's all the progress I've made. Also, getting iPhone apps to run in the Aspen simulator doesn't seem to work either because the Aspen apps are compiled with a different platform configuration and are completely different from the UIKit Apps. The few apps that are available, MobileSafari and the like, have been compiled for AspenSimulator by Apple.

    Oh, and I'm also planning on buying the 1.2 beta (the $99 one) so I maybe able to get the apps to run on earlier firmwares by screwing with the frameworks, if that doesn't breach some sort of NDA or whatever.
    I've spent most of my time developing in Java so all this stuff is a bit new. But from what I understand (and what you've just said) Aspen Simulator compiles stuff for intel proccessors, while when you click to compile for aspen it actually compiles for the iphone ARM processor.

    I guess this leaves two main questions:
    1.) Can we copy all the files from the Aspen.platform directory to our iPhones and run the new OS.

    2.) Can we copy our framework files from out iphones to the aspen folder and compile for our current iphone firmware.

    I'm thinking about trying #2, but I'm afraid of #1.

    Someone should host a IRC for this so we can make some real progress.

  16. #16
    OK, so I've tried some things.
    I tried dumping all the frameworks off a 1.1.4 decrypted ipsw into the Aspen sdk and replacing the old ones, and then replacing Xcode's gcc-4.0 with the old Dev Team SDK's arm-apple-darwin-gcc. Then I built but received some missing lib errors, which I supplied from the 1.1.4 image. That led to about 40 errors regarding missing symbols, so no go there.
    Then I tried replacing the old frameworks into Aspen and using the arm-apple-darwin-gcc instead of gcc-4.0 which allowed the app to build (as Release, for Device, not simulator). However, it still crashes on my phone and I still get some error about certification when building for Debug.

    Anyone else make any progress?


    Anshu Chimala
    Follow @anshuchimala on Twitter
    Visit http://www.airpoke.com, my latest project for iPhone/iPod touch.

  17. The Following User Says Thank You to Drakenza For This Useful Post:

    Iman07 (2008-03-08)

  18. #17
    Well it's probably a horrible idea, but we ought to try coping over all the frameworks and components from the Aspen.platform onto a iPhone or iPod Touch and see what happens, that process would probably be easier if we new how to mod the OS while it's running

  19. #18
    Quote Originally Posted by spiraldark View Post
    I've spent most of my time developing in Java so all this stuff is a bit new. But from what I understand (and what you've just said) Aspen Simulator compiles stuff for intel proccessors, while when you click to compile for aspen it actually compiles for the iphone ARM processor.

    I guess this leaves two main questions:
    1.) Can we copy all the files from the Aspen.platform directory to our iPhones and run the new OS.

    2.) Can we copy our framework files from out iphones to the aspen folder and compile for our current iphone firmware.

    I'm thinking about trying #2, but I'm afraid of #1.

    Someone should host a IRC for this so we can make some real progress.
    #1 will not work. You need the 1.2 kernel. I have no clue why, but it's like 1.1.3 and the rented movies, only this time, your iPhone won't even run. Plus, there is more to frameworks than just the binaries that you could be missing, and you can't get those.

    To clear things up...

    Aspen Simulator = Intel (Computer)
    Aspen = ARM (iPhone)


    Quote Originally Posted by Drakenza View Post
    OK, so I've tried some things.
    I tried dumping all the frameworks off a 1.1.4 decrypted ipsw into the Aspen sdk and replacing the old ones, and then replacing Xcode's gcc-4.0 with the old Dev Team SDK's arm-apple-darwin-gcc. Then I built but received some missing lib errors, which I supplied from the 1.1.4 image. That led to about 40 errors regarding missing symbols, so no go there.
    Then I tried replacing the old frameworks into Aspen and using the arm-apple-darwin-gcc instead of gcc-4.0 which allowed the app to build (as Release, for Device, not simulator). However, it still crashes on my phone and I still get some error about certification when building for Debug.

    Anyone else make any progress?
    This will not work, because remember, the Simulator files are for Intel. ARM on the other hand, I don't know why it won't work with that.
    Last edited by King Chronic; 2008-03-10 at 12:40 PM. Reason: Automerged Doublepost

  20. #19
    didnt someone already break the drm code needed for the apps to work after you create them on the sdk, about a month ago.

    http://www.austinheap.com/assets/isdk/


    here it is I dont know how to use it but here it is according to tuaw
    Last edited by joejoe123; 2008-03-11 at 12:20 AM. Reason: Automerged Doublepost

  21. #20
    Quote Originally Posted by joejoe123 View Post
    didnt someone already break the drm code needed for the apps to work after you create them on the sdk, about a month ago.

    http://www.austinheap.com/assets/isdk/


    here it is I dont know how to use it but here it is according to tuaw
    DRM isn't the issue, it's the lack of 1.2.0 firmware (or maybe they're feeling special and it really is 2.0.0 firmware).

    Also, as a side note, Aspen Simulator has universal binaries, along with the whole SDK. I posted on another topic in this SDK forum with a solution for PowerPC users. Apple just didn't want to admit it?

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