Updated Troubleshooting (markdown)

LukeeGD 2022-07-21 12:07:00 +08:00
parent 7b7f62ebef
commit 3532181060

@ -15,19 +15,20 @@
- If you want to go back and restore to iOS 7.1.2, you need to disable the exploit
- From the main menu, select "Disable/Enable exploit" > "Disable exploit"
- If disabling the exploit did not work: [Follow the steps for Clearing NVRAM](#clearing-nvram)
- This script uses an older Linux compiled version of ch3rryflower and automates the downgrade process for the iPhone 4
- This script uses powdersn0w (or for iOS 4.3.x, an older Linux compiled version of ch3rryflower) and mostly automates the downgrade process for the iPhone 4
- Windows users can create a Linux live USB (see Requirements)
- macOS users should use [cherryflowerJB](https://web.archive.org/web/20210322151509/https://dora2ios.web.app/CFJB/) or [powdersn0w](https://dora2ios.web.app/konayuki/index.html) instead of iPhone4Down for more support
- Only iPhone4Down functions on macOS are restoring to iOS 7.1.2 (can be with jailbreak option enabled), restoring with blobs, and entering kDFU mode
- macOS users should use [cherryflowerJB](https://web.archive.org/web/20210322151509/https://dora2ios.web.app/CFJB/) or [powdersn0w](https://dora2ios.web.app/konayuki/index.html) instead of iPhone4Down for better support
- Only iPhone4Down functions fully supported on macOS are restoring to iOS 7.1.2 (can be with jailbreak option enabled), restoring with blobs, and entering kDFU mode
- **This supports the iPhone 4 GSM (iPhone3,1) only**
- Only restoring with blobs and entering kDFU mode supports all iPhone 4 models
- iPhone4Down may be updated with iPhone3,3 support when the exploit file needed for powdersn0w gets released
- iPhone4Down may be updated with iPhone3,3 support when the exploit file needed for powdersn0w gets released
- The downgrades have the option to jailbreak
- 8GB models may not work with downgrades below iOS 6
- Newer models may not work with downgrades below iOS 5
- It is recommended to use an Intel PC/Mac as entering pwnDFU can be a lot more unreliable on devices running AMD CPUs (this includes encounter "Segmentation fault" errors with pwnedDFU)
- You NEED a working Home and Top/Power button to enter proper DFU mode in order to use ch3rryflower/iPhone4Down. kDFU mode will NOT work!
- Disabling the memory option does not actually work properly on iPhone4Down (ch3rryflower), so users with not enough RAM may encounter problems in creating custom IPSW
- If your device is not compatible as mentioned above, you will get the error "could not retrieve device serial number"
- It is recommended to use an Intel PC/Mac as entering pwnDFU can be a lot more unreliable on devices running AMD CPUs (this includes encountering "Segmentation fault" errors with pwnedDFU)
- You NEED a working Home and Top/Power button to enter proper DFU mode in order to use iPhone4Down. kDFU mode will NOT work!
- Disabling the memory option does not work properly on iPhone4Down when ch3rryflower is used (iOS 4.3.x), so users with not enough RAM may encounter problems in creating custom IPSW
## macOS
- macOS users may have to install libimobiledevice and libirecovery from [Homebrew](https://brew.sh/) or [MacPorts](https://www.macports.org/). This is optional, but recommended if you are having any issues.
@ -48,7 +49,7 @@
## Windows
- **I highly recommend Windows users to use iOS-OTA-Downgrader on Linux or macOS instead.** You may create a Linux live USB, and this can easily be done with tools like [Ventoy](https://www.ventoy.net/).
- **Support for A7 devices is limited.** More details below.
- There are multiple features of iOS-OTA-Downgrader that are not supported on Windows. This includes "Other" restores with SHSH blobs, all functions of iPhone4Down, and A7 device support.
- There are multiple features of iOS-OTA-Downgrader that are not supported on Windows. This includes "Other" restores with SHSH blobs, most functions of iPhone4Down, and A7 device support.
- Custom IPSWs created in the Windows version are NOT compatible with Linux/macOS futurerestore.
- For 32-bit devices: Note that in the Windows version, the current baseband of your device will be left intact, unlike in Linux/macOS where the latest baseband always gets flashed.
- It is recommended that users restore to the latest version (9.3.6 or 10.3.4) first before downgrading in order to have the latest baseband.