The problem with this second method is, Apple uses the same info as the Activation Request, with only minimal changes. The second method is a simple CertifyMe request generated on the device and is sent to the Apple server, a.k.a., 'Albert'. Following is an example of the activation process and how Apple verification takes place. The first one is in the Activation itself.

So the old doulCi that i have decided to rename again because of scammers to 'Merruk iCloud Bypass' is still working, with some exceptions, because Apple added some security patches on both the server side and in its iOS.Īpple used two methods for the certification of its iDevices. To be fully patched it would require Data Migration, which would be very time and labor consuming for Apple and would require a great deal of effort.

The first one is a 'CertifyMe' exploit and the second is based on a security flaw on Apple servers that was actually a beginner?s mistake. After that, someone else going by the name of minacriss discovered one of the two exploits used by this bypass. It was discovered, developed and demoed by Yahya Lmallas during the first months of 2014. It had the simple name 'doulCi', a reverse spelling of iCloud. Is 'Merruk iCloud bypass' real? Is it still working? So, how can I be sure?ĭoulCi kitchen, a.k.a 2.0, was an improved version of the old magic line way method of bypassing Apple's iCloud Activation lock. Merruk iCloud bypass detailed technical instructions: From the beginning.

ICloud bypass is no longer called doulCi, it goes Open Source with the name merruk iCloud bypass

Download doulci icloud bypass tool