QUOTE
We are arguing about the definition of IPSW and Firmware, apparently you argued that you cant used these two terms interchangably, when i say they are both the same thing. Hence why this:-
I know about the whole payload system and your notion of a custom "firmware" (okay, we'll use YOUR term), i've used iPlus before to unlock my own re-updated 1.1.4. The whole confusion here is about "definition", not the methods.
Did i said we can't use the two terms interchangably? Hmmm ..

. I agree with u that IPSW = firmware (IPSW is the file format that contains the firmware ... or izzit im still confuse?). Thats why i use it interchangably. Sorry to other forumer if by my action of using those 2 terms confuses u all. My bad. I should just stick to one format since both thing means the same.

. And there is no MY term or YOUR term or ANYONES term. Just the universal iPhone term. I understand what the "Definition" is and yes .. i was talking about the method and not the definition.
QUOTE
Apparently your sarcasm meter is broken, coz i posted that sarcastically. Any clearer would make the post not work "sarcastically".
Its not broken but asleep

but my other meters and functions are still working fine.
QUOTE
I suggest you reread what i posted from post #11. Hell, my Post #11 itself described your interest in what you define as "custom firmware", but what i call "customised .IPSW", when we are talking about the same thing. My gripe with you is that in one post you wrote "custom firmware", then later "custom IPSW" then on another on the same post itself , you wrote "custom IPSW firmware". Getting your terms and definition right would help in conveying your message across and not confusing others and yourself.
And i suggest u re-read post #10. Yeah the one before u.
QUOTE
If Apple can include new apps inside new official firmwares from Apple (iTunes Wifi Store, Apps Store, etc), i assume you could add your own 3rd party apps inside the .ipsw package, once it has been Pwnaged? That's "custom" by my definition anyway.
In this statement ... you assumed that we can add our own 3rd party apps inside the .ipsw package which is correct hence your definition of "custom" .ipsw package or firmware (what ever u wanna call it).
QUOTE
About loading custom firmwares i.e. our apps and all for backup, I don't see any features to do so. Am i missing something? Looks like the IPSW builder only have the option to jailbreak, activate, unlock and put boot neuter in it.
In my statement ... I was wondering about the "IPSW builder" in the pawnage tool itself. If u look carefully in the video, there's no option to put our own 3rd party apps (like u mention above) in the .ipsw package. It looks like the "IPSW builder" only limited to repackaging the .IPSW package with a pre-jailbreak, pre-activate and pre-unlock files in it plus the bootneuter app (which is the only 3rd party app available in the "IPSW Builder"). I was concentrating more on the TOOL itself rather that the definition. This was cleared up by SEP10 from his link to the "IPSW tool" (read that carefully ... later u say i use "IPSW builder" then "IPSW tool" then "IPSW builder" then "IPSW tool" ... which is not the same thing or tools) by chronic dev that can package our 3rd party apps in the .ipsw package which "IPSW builder" can't do. Hope other forumer don't get confuse ... later habis i kena lagi.
QUOTE
Let me put it in bullet points:-
1. I talked about "Pwning an .IPSW package with addition of your own 3rd party apps".
And I talked about "IPSW builder" in the pwning (pawnage) tool that can't package additional 3rd party apps besides bootneuter in it .... YET.2. You then talked about "custom IPSW" which is the same thing as what i mean, only that you elaborated further with using the payload system modeled after the iLiberty/iPlus to make every restores easier. I admit i should have elaborated further on my Point #1 there, but that is basically what i mean.
Agreed with you on this point and this is the starting point of the confusion3. The whole thread after this went into a spiral dive about one person thinking that the other person has it all wrong, when they are both thinking about the same thing.
Bound to happen when people discussing about a new tool thats not been personally tested yet and doing so while our biological clock was screaming for us to go to sleep. Don't u agree?Are we on the same page now?
But i see something good about all this, at least we have a healthy discussion about this, rather than a one-way communication. I applaud your enthusiasm and effort in engaging this discussion, unlike others who stop dead in their tracks once something on the contrary to their beliefs or way of thinking , hit them.

Sometime people just don't take the pride to stood by their beliefs (if they 100% confirm its right la). I love discussing this ... with it we can gather more info or corrected our misguided view (if there's any).
BTW u should've been a prosecution lawyer instead of a pilot

(my sarcastic meter just woke up) Hehehehehehe.
Added on April 4, 2008, 2:33 amQUOTE(LaskarCinta @ Apr 4 2008, 01:36 AM)
nyum nyum, with iPhone Pwn has been released, y not they leak the firmware 1.2 already? or the second beta 2.0 that has already being seeded by Apple just days b4? some people needs Exchange goodness, hehehe...
or maybe another 2 months isn't that long for the official ones? hihihi...
Use the 1.2 firmware or 2.0 only if you are a authorize developer from the SDK program. If your not a developer then better don't as its a copyright infringement. And I suggest to all forumer that have the "dirty" idea to download the "leak" firmware not to do it. If u do your research ... firmware 1.2 or 2.0 are still not stable enough for daily usage. Its design as a testing platform for the SDK apps, CISCO VPN and MS Exchange functionality. U won't get any benefit from it but more headache. Just be patient and wait for the official one which is another 2 months. Pejam celik pejam celik sudah 2 bulan.
This post has been edited by frozzbyte: Apr 4 2008, 02:33 AM