diff --git a/README.md b/README.md index 50caee4..55205bc 100644 --- a/README.md +++ b/README.md @@ -1,23 +1,5 @@ -
- Logo -
- -

- Documentation • - Installation Guide • - Requirements • - Support Discord • - Website -

- -## Information -This is the official repo for the palera1n project, a jailbreak for arm64 devices on iOS 15.0+ - -- Loader application used in palera1n can be found [here](https://github.com/palera1n/loader). -- palera1ns jbinit can be found [here](https://github.com/palera1n/jbinit). -- palera1ns custom PongoOS can be found [here](https://github.com/palera1n/pongoos). - -Website & credits can be found at https://palera.in (scroll down for credits). +# palera1n +This is the official repo for the palera1n jailbreak, a jailbreak for A8 through A11 devices, on iOS 15.0 and higher. ## Warnings We are **NOT** responsible for any data loss, or the result of a device being bricked. The user of this program accepts responsibility should something happen to their device. While nothing should happen, jailbreaking has risks in itself. @@ -31,7 +13,8 @@ We are **NOT** responsible for any data loss, or the result of a device being br - A checkm8 vulnerable iOS device on iOS 15+ (`A8` - `A11`) - On `A11`, **you must disable your passcode while in the jailbroken state** (on iOS 16, you need to **reset your device** before proceeding with palera1n). -- **USB-A** cables are recommended to use, USB-C may have issues with palera1n and getting into DFU mode.
Technical explanationThe BootROM will only enter DFU if it detects USB voltage, which boils down to checking whether a certain pin is asserted from the Tristar chip. The Tristar does this based on the cable's accessory ID, and apparently USB-A and USB-C cables have different accessory IDs, and the one of the USB-C cables makes the Tristar not assert the USB voltage pin.
+- **USB-A** cables are recommended to use, USB-C may have issues with palera1n and getting into DFU mode. +
Technical explanationThe BootROM will only enter DFU if it detects USB voltage, which boils down to checking whether a certain pin is asserted from the Tristar chip. The Tristar does this based on the cable's accessory ID, and apparently USB-A and USB-C cables have different accessory IDs, and the one of the USB-C cables makes the Tristar not assert the USB voltage pin.
- A Linux or macOS computer - AMD CPUs (not AMD Mobile) have an issue [with (likely) their USB controllers] that causes them to have a very low success rate with checkm8. It is not recommended that you use them with palera1n. @@ -41,14 +24,13 @@ We are **NOT** responsible for any data loss, or the result of a device being br - USB-C port on Apple Silicon Macs may require manual unplugging and replugging of the lightning cable after checkm8 exploit. - This problem may be solved by connecting via USB hub, though extensions can vary. -## Need help? +## Troubleshooting -Make sure you provide full details on your device, such as: -- iDevice +Make sure you're following the guides provided [here](https://palera.in), also when asking for support make sure you provide full details on your device, such as: +- iPhone/iPad/iPod - iOS Version - Passcode enabled? -- Logs, if panicked then send latest `panic-full` log from your iDevice. +- Verbose from palera1n (specifying `-Vv` within palera1n) +- Panic logs, if panicked then send latest `panic-full` log from your device. -Using `-VvL` would help with debugging. - -Join the [Support Discord](https://dsc.gg/palera1n) +Then join the [Support Discord](https://dsc.gg/palera1n)