From 520d79b3993486449885758f0c66100d7a92da21 Mon Sep 17 00:00:00 2001 From: BananaOnGitHub Date: Mon, 13 Feb 2023 23:05:58 -0600 Subject: [PATCH] Update README.md --- README.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index ee4a20e..6510245 100644 --- a/README.md +++ b/README.md @@ -15,18 +15,20 @@ ### You can obtain v2.0.0 beta [here](https://github.com/palera1n/palera1n-c/releases). # Warnings -- This palera1n rewrite has noticeably different arguments compared to older palera1n, would recommend you take a look at how to use palera1n-c [here](https://cdn.nickchan.lol/palera1n/c-rewrite/releases/v2.0.0-beta.1/palera1n.1.html). +- This palera1n rewrite has noticeably different arguments compared to the shell version of palera1n. + - Highly recommended that you take a look at how to use palera1n-c [here](https://cdn.nickchan.lol/palera1n/c-rewrite/releases/v2.0.0-beta.1/palera1n.1.html). - This does **NOT** support tethered creation or booting. You must use the older [shell version of palera1n](https://github.com/palera1n/palera1n). -- 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. If your device is stuck in recovery, please run futurerestore `--exit-recovery`, or use `irecovery -n`. +- 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. + - If your device is stuck in recovery, please run futurerestore `--exit-recovery`, or use `irecovery -n`. -- palera1n-c will never work in VirtualBox, VMware or any virtual machine that doesn't support a PCI passthrough. +- palera1n-c will never work in VirtualBox, VMware or any virtual machine that doesn't support PCI passthrough. # Requirements -- Needs a checkm8 vulnerable iOS device on iOS 15.x or 16.x (`A8` - `A11`) - - If using Rootful, **you will need 5-10GB of space** for the fakefs. This means that 16GB devices cannot be semi-tethered with Rootful. - - 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 `A11`). +- A checkm8 vulnerable iOS device on iOS 15.x or 16.x (`A8` - `A11`) + - If using rootful, you will need **5-10GB of space** for the fakefs. This means 16GB devices cannot use the full fakefs creation. However, you can change the arguments to `-Bf` to create a fakefs with bind mounts, so it uses a smaller size, at the expense having unwritable parts in rarely-written paths, and then boot it + - 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.