iphone-hacks.com

killacam13 · 2008-07-25 15:48:23

I hear this all the time. It’s simple. Ziphone does permanent changes to your phone. Zibri is a terrible coder that stole most the exploits for ZiPhone and did not create them. Zibri admits that he cannot code. Ziphone does work most of the time. But when it does not work, you are most likely left with an unfixable brick. Other jailbreak software such as iLiberty+, Pwnage, will not leave you with a brick. Everything they do can be reverted safely. This means if they fail on you, you just restore and try again. No harm done.

With ziphone, your damage is permanent. It’s a crap shoot. It may work 9 times out of 10, but on that 10th time that it fails out, you can expect to be purchasing a new iPhone. Sounds great right? Indeed, this is so common that the term “ziphoned” actually has meaning (a bricked phone caused by ZiPhone). Check out the google search on the term and see the problems for yourself.

If you have used Ziphone and your phone is currently working, you do not need to do anything. Just don’t use it again. The next time could be fatal. You’ve been warned!

Question:

Could you please elaborate on the permanent changes caused by Ziphone?
All unlocking/jailbreaking methods modify the phone in some way, at least they patch baseband, and pwnage patches bootloader.
I know that Ziphone downgrades the 4.6 bootloader to 3.9 (which has been thought to be permanent until pwnage came out), but so does iLiberty+, iDemocracy and any other unlock method that is not based on pwnage

Answer:

First off, iLiberty+ does not downgrade your bootloader by default. It downgrades you to 3.9 fakeblank which is easily reversible and not dangerous. This is not the same thing as 3.9 used by Ziphone! Ziphone downgrades the bootloader to 3.9 automatically. If this process fails, you’re done. This process considered so risky that Apple does not do any bootloader upgrades in their firmware packages! They could have put a stop to all the unlocks when 1.1.2 came out by having the 1.1.1 to 1.1.2 firmware upgrade upgrade old bootloaders to 4.6 but they considered this too risky and did not do it! Ziphone does it anyway.

Zibri has had so many releases that fix “type-o’s”. That’s just silly. The code is so sloppy and buggy. Some versions will unlock even when you did not ask it to resulting in a downgraded bootloader just on a request to jailbreak! Neat

Ziphone is also very dangerous because it does all the flashing (most risky part) during the first phase of the ram disk. During this phase, allocating too much memory can result in ram disk corruption. This is very bad. You want to minimize the amount of memory used as much as possible and you only care about stability. Ziphone doesn’t worry about this. Due to the technique used to boot the ramdisk, the memory is easily corrupted if you try to allocate too much of it. The result is that you are corrupting the very data that you are flashing!

iLiberty+, iPlus both use a smaller ram disk to flash. This minimizes the amount of memory used and takes great care to prevent memory allocations from corrupting the ram disk. Then these tools come back on a second pass to install payloads. This is done after the flashing is done where there is no risk.

As a result, several ziphone users have reported problems with no edge, no wifi, no bluetooth or a combination of the 3. In many cases this is unfixable. Zibri has added a wifi “fix” to his app which works sometimes, but this programs a bogus network address that is the same on every phone.

Great explanation from sleepers

nedthehead · 2008-07-25 16:02:58

Interesting/ I'm using WinPwn 2.0.0.3 now, so sounds like I'm safe

Mes · 2008-07-25 17:53:11

Thanks killacam13 for explaining some of the differences between the various methods. It's obvious how the ram allocation method could result in a whole range of problem/corruption issues.

I have a follow-up question. Referring to a 2G-8GB model: IF Ziphone was successful, which you stated is 9 out of 10 times ---- are there any lingering issues and/or areas to watch when upgrading to 2.0?

One of these days I will upgrade a Z'd iPhone from 1.1.4 to 2.0. Reports seem very positive, but it's not clear where those upgraded iPhones were or how they got there prior to the 2.0 upgrade. Do you have any experience with these details that you could share? BTW: My desire is to use the more popular (and probably safer (Pwnage) method for my eventual upgrade.

Thanks in advance,

Mes

Last edited by Mes (2008-07-25 17:55:58)

killacam13 · 2008-07-26 03:58:55

i havent used ziphone since 1.1.2..thats when i found out what i have found out...so i wouldnt quite no

but i will say that before you use pwnage or any other hack DFU restore to an official firmware to get rid of all that ziphone foolery...then pwn it and flash custom firmware

Last edited by killacam13 (2008-07-26 03:59:14)

jaiy2kkumar · 2008-09-16 01:18:08

I just downloaded ziphone but i never used it on my i phone. thanks a lot bro.

Franny · 2008-09-16 05:17:34

Delete that ZiPhone.

structure75 · 2008-09-19 22:06:13

Mes wrote:
Thanks killacam13 for explaining some of the differences between the various methods. It's obvious how the ram allocation method could result in a whole range of problem/corruption issues.

I have a follow-up question. Referring to a 2G-8GB model: IF Ziphone was successful, which you stated is 9 out of 10 times ---- are there any lingering issues and/or areas to watch when upgrading to 2.0?

One of these days I will upgrade a Z'd iPhone from 1.1.4 to 2.0. Reports seem very positive, but it's not clear where those upgraded iPhones were or how they got there prior to the 2.0 upgrade. Do you have any experience with these details that you could share? BTW: My desire is to use the more popular (and probably safer (Pwnage) method for my eventual upgrade.

Thanks in advance,

Mes

I was wondering if you have upgraded your Z'd iphone from 1.1.4 to 2.0 yet? I'm in the same situation.

Diabloghst · 2008-09-19 22:17:45

structure75 wrote:
Mes wrote:
Thanks killacam13 for explaining some of the differences between the various methods. It's obvious how the ram allocation method could result in a whole range of problem/corruption issues.

I have a follow-up question. Referring to a 2G-8GB model: IF Ziphone was successful, which you stated is 9 out of 10 times ---- are there any lingering issues and/or areas to watch when upgrading to 2.0?

One of these days I will upgrade a Z'd iPhone from 1.1.4 to 2.0. Reports seem very positive, but it's not clear where those upgraded iPhones were or how they got there prior to the 2.0 upgrade. Do you have any experience with these details that you could share? BTW: My desire is to use the more popular (and probably safer (Pwnage) method for my eventual upgrade.

Thanks in advance,

Mes
I was wondering if you have upgraded your Z'd iphone from 1.1.4 to 2.0 yet? I'm in the same situation.

like killacam said. dont upgrade but instead restore so that u have a fresh new clean slate to work with and then use winpwn never ziphone

Mes · 2008-09-22 15:55:58

structure75 wrote:
Mes wrote:
Thanks killacam13 for explaining some of the differences between the various methods. It's obvious how the ram allocation method could result in a whole range of problem/corruption issues.

I have a follow-up question. Referring to a 2G-8GB model: IF Ziphone was successful, which you stated is 9 out of 10 times ---- are there any lingering issues and/or areas to watch when upgrading to 2.0?

One of these days I will upgrade a Z'd iPhone from 1.1.4 to 2.0. Reports seem very positive, but it's not clear where those upgraded iPhones were or how they got there prior to the 2.0 upgrade. Do you have any experience with these details that you could share? BTW: My desire is to use the more popular (and probably safer (Pwnage) method for my eventual upgrade.

Thanks in advance,

Mes
I was wondering if you have upgraded your Z'd iphone from 1.1.4 to 2.0 yet? I'm in the same situation.

I upgraded to 2.1 a few days ago.

I followed the instructions using PwnageTool_2.1 on the Mac .... with success.

At 1st, I tried to do this on my PC, 1st creating a custom 2.1 restore pkg on the mac, and use iTunes 8 on my PC to restore this custom file .. got 1600 errors. Ugg. (absolutely, positively in DFU mode regardless of what the error says). Tried it 3 times. But luckily I have a Mac ..... and success with PwnageTool 2.1.

Note: After installing 2.1 --- Back to my PC. Sync with iTunes 8 worked remarkably well. Contacts, SMS & Mail settings, even app locations on Springboard. 1.1.4 to 2.1. When restore works, it works great !! (of course, no pre-2.x apps installed -- but I've found almost everything I need on AppleStore and Cydia, and the rest of my custom mods were either simple plist mods or file additions using SSH)

Last edited by Mes (2008-09-22 16:06:26)

Aliandro Operator · 2008-09-22 16:30:20

Well congragulations on that, my friend!
Glad it all worked for you.
If anything pops up please do ask on the forum.
And also be active on it! xD

Have fun with your newly updated iPhone!

The Operator.

highlander · 2008-10-23 00:30:35

what about quickpwn????

Is it the same thing???

I have my jailbroken phone with quickpwn

Diabloghst · 2008-10-23 02:46:51

dude ziphone is outdated so... quickpwn is fine

Aliandro Operator · 2008-10-23 19:19:19

As stated, QuickPwn/WinPwn/Pwnage/iLiberty/iBricker/i(something here)/etc etc etc, dont use the same coding as ZiPhone, as in, they dont do the same thing. They do reach to the same goal, but not by the same means of reaching it.

Your safe as long as you use any of those programs mentioned in my post, or in Killacam's.

The Operator.

iphone-hacks.com

Announcement

#1 2008-07-25 15:48:23

“But Ziphone works fine for me? Why should I avoid it?”

#2 2008-07-25 16:02:58

Re: “But Ziphone works fine for me? Why should I avoid it?”

#3 2008-07-25 17:53:11

Re: “But Ziphone works fine for me? Why should I avoid it?”

#4 2008-07-26 03:58:55

Re: “But Ziphone works fine for me? Why should I avoid it?”

#5 2008-09-16 01:18:08

Re: “But Ziphone works fine for me? Why should I avoid it?”

#6 2008-09-16 05:17:34

Re: “But Ziphone works fine for me? Why should I avoid it?”

#7 2008-09-19 22:06:13

Re: “But Ziphone works fine for me? Why should I avoid it?”

Mes wrote:

#8 2008-09-19 22:17:45

Re: “But Ziphone works fine for me? Why should I avoid it?”

structure75 wrote:

Mes wrote:

#9 2008-09-22 15:55:58

Re: “But Ziphone works fine for me? Why should I avoid it?”

structure75 wrote:

Mes wrote:

#10 2008-09-22 16:30:20

Re: “But Ziphone works fine for me? Why should I avoid it?”

#11 2008-10-23 00:30:35

Re: “But Ziphone works fine for me? Why should I avoid it?”

#12 2008-10-23 02:46:51

Re: “But Ziphone works fine for me? Why should I avoid it?”

#13 2008-10-23 19:19:19

Re: “But Ziphone works fine for me? Why should I avoid it?”

Board footer