Uploaded December 2015 | Updated September 2026, 44 minutes ago
IMPORTANT!!! Please note that this video is for educational purpose only. By watching this video, you agree that I'm not responsible of what might happen with the use of informations provided.
WARNING : This video involves hacking on Low-Level parts of iOS. Unlike userland, those parts contains lot of critical informations about the device's hardware, which could be corrupted and lead to a hard brick if something goes wrong by following instructions provided in this video.
From a jailbroken iOS 7.1.2 kernel on which TaskforPid() is patched, Winocm's Kloader can be executed to bootstrap the beginning of another iOS bootchain instance (in this video, it's an iOS 6.1.3 one). The ARM image usually used with kloader is iBSS, from the DFU Bootchain. Most Kloader bootstraps use DFU Bootchain's images even if it is also possible to use Flashed Bootchain ones, which are usually more complete (like flashed iBoot can interact with File System, while iBEC can't). DFU one usually involve more loading in memory than Flashed Bootchain, which is more File System friendly. Once Kloader did it's magic and loaded iBSS, we have to send to it iBEC ARM image, the second stage of the DFU Bootchain. The LCD screen of the iOS device light up when iBEC is launched. Now the most interesting part begins. We have to send to iBEC each boot components in a specific order. First, send and execute the DeviceTree. Second, send and load a Ramdisk (seems to make no sense because we want to boot the File System, but there is something tricky here). Third, send the iOS Kernel and launch it using "bootx".
If you do those steps using original decrypted and patched files, without patching boot-args, this will load the restore Ramdisk. If you don't specify a Ramdisk in steps above, this will load the File System, but without taking in consideration boot-args (no verbose boot). If you open the decrypted iBEC file using a Hex editor, you will notice that boot-args are set like that : rd=md0 nand-enable-reformat=1 -progress. Those are boot-args used when booting a Ramdisk. If we change this boot-args string to : "-v", iBEC will load the File System by default, because we removed "rd=md0" which sets the RootDevice to "MemoryDevice0", which is the Ramdisk. It's also possible to change the default root device by adding "rd=[Root Device]" in iBEC's boot-args string.
Limera1n BootROM exploit is superior than Kloader. It acts directly from DFU mode, so an installed Operating System is not required. In the second part of this video, I simply use RedSn0w jailbreak utility to inject Limera1n over the DFU Mode. The root device is set to the iOS 5.1.1 filesystem in iBEC's boot-args. Then, RedSn0w will automatically send and execute each bootloaders in their respective order.
IMPORTANT!!! Please note that this video is for educational purpose only. By watching this video, you agree that I'm not responsible of what might happen with the use of informations provided.
WARNING : This video involves hacking on Low-Level parts of iOS. Unlike userland, those parts contains lot of critical informations about the device's hardware, which could be corrupted and lead to a hard brick if something goes wrong by following instructions provided in this video.
From a jailbroken iOS 7.1.2 kernel on which TaskforPid() is patched, Winocm's Kloader can be executed to bootstrap the beginning of another iOS bootchain instance (in this video, it's an iOS 6.1.3 one). The ARM image usually used with kloader is iBSS, from the DFU Bootchain. Most Kloader bootstraps use DFU Bootchain's images even if it is also possible to use Flashed Bootchain ones, which are usually more complete (like flashed iBoot can interact with File System, while iBEC can't). DFU one usually involve more loading in memory than Flashed Bootchain, which is more File System friendly. Once Kloader did it's magic and loaded iBSS, we have to send to it iBEC ARM image, the second stage of the DFU Bootchain. The LCD screen of the iOS device light up when iBEC is launched. Now the most interesting part begins. We have to send to iBEC each boot components in a specific order. First, send and execute the DeviceTree. Second, send and load a Ramdisk (seems to make no sense because we want to boot the File System, but there is something tricky here). Third, send the iOS Kernel and launch it using "bootx".
If you do those steps using original decrypted and patched files, without patching boot-args, this will load the restore Ramdisk. If you don't specify a Ramdisk in steps above, this will load the File System, but without taking in consideration boot-args (no verbose boot). If you open the decrypted iBEC file using a Hex editor, you will notice that boot-args are set like that : rd=md0 nand-enable-reformat=1 -progress. Those are boot-args used when booting a Ramdisk. If we change this boot-args string to : "-v", iBEC will load the File System by default, because we removed "rd=md0" which sets the RootDevice to "MemoryDevice0", which is the Ramdisk. It's also possible to change the default root device by adding "rd=[Root Device]" in iBEC's boot-args string.
Limera1n BootROM exploit is superior than Kloader. It acts directly from DFU mode, so an installed Operating System is not required. In the second part of this video, I simply use RedSn0w jailbreak utility to inject Limera1n over the DFU Mode. The root device is set to the iOS 5.1.1 filesystem in iBEC's boot-args. Then, RedSn0w will automatically send and execute each bootloaders in their respective order.




![Triple Boot iOS 7.1.2, iOS 6.1.3 and iOS 5.1.1 on iPhone 4 (N90AP)
IMPORTANT!!! Please note that this video is for educational purpose only. By watching this video, you agree that Im not responsible of what might happen with the use of informations provided.
Also, please note that this video is a demonstration, not a tutorial. Set up a triple boot like this one can take few hours, depending on many technological factors. Maybe a day I will release a complete tutorial about how to do it.
In this video, Im doing a triple boot between iOS 7.1.2 (signed), 6.1.3 and 5.1.1 on an iPhone 4 (N90AP). From the power button, the device boots on iOS 7.1.2, which is correctly signed. Then, I use RedSn0ws Tethered Boot function to inject Limera1n exploit over the DFU mode and allow an unsigned (patched) iOS 6.x bootchain to be executed. The root device has been set to the partition which contains iOS 6.1.3 file system in iBECs boot-args string. The kernel will search for launchd on that partition. Then, iOS 6.1.3 starts up. The modem (baseband) works properly, it can receive calls. Over all, the firmware is really stable.
After, I use again RedSn0ws Tethered Boot function to inject Limera1n exploit over the DFU mode and allow an unsigned (patched) iOS 5.x bootchain to be executed. The root device has been set to the partition which contains iOS 5.1.1 file system in iBECs boot-args string. The kernel will search for launchd on that partition. Then, iOS 5.1.1 starts up. The modem (baseband) works properly, it can receive calls. Over all, the firmware is really stable, but some old applications like YouTube, or old versions like the AppStore and iTunes Store are a bit broken.
Special thanks to @iH8Sn0w for advices about the kb_load(), this helped me with my research about.
iOS Multi-Booting status list :
A4 SecureROM and less, Multi-Booting 5.x and newer, with 4.x and lower using DFU Limera1n exploit [FAILED]
A4 SecureROM and less, Multi-Booting similar iOS versions (like 5.x and 6.x) using DFU Limera1n exploit [PASS]
iPhone 4 (N90AP), Multi-Booting iOS 7.x with lower using DFU Limera1n exploit [PASS]
A5 SecureROM and up (32-bits), Multi-Booting really similar iOS versions (6.1.3 and 6.0) using kloader bootstrap method [PASS]
A5 SecureROM and up (32-bits), Multi-Booting 6.1.3 with 5.x using kloader bootstrap method [CURRENTLY WORKING ON]
A5 SecureROM and up (32-bits), Multi-Booting 6.1.3 with 7.x and newer using kloader bootstrap method [FAILED]
A5 SecureROM and up (32-bits), Multi-Booting 9.x with 7.x using kloader bootstrap method [FAILED] Triple Boot iOS 7.1.2, iOS 6.1.3 and iOS 5.1.1 on iPhone 4 (N90AP)](https://i.ytimg.com/vi/qtZUZ4RYzAY/mqdefault.jpg)
![Crash Team Racing - Nitro Oxide in Adventure Mode
English:
Here is a Crash Team Racing video showing the character Nitro Oxide playable only with an Action Replay/GameShark code. This code replace the graphics of the normal character you are playing in adventure mode with Nitro Oxides graphics because when a jump is performed with Oxide, we can see the shadow of a regular kart. Also, with this code, the game will crash at several places in the game such as when the character selection screen appears (in all game modes) and also when you leave the castle square in adventure mode.
I play with the NTSC [U] version of the game and the code I used is 80086E84 000F. You must save your game in the castle area, otherwise the game will crash.
Français:
Voici une vidéo présentant le personnage Nitro Oxide du jeu Crash Team Racing pour Playstation jouable uniquement avec un code Action Replay/GameShark. Ce code permet de remplacer limage du personnage avec lequel vous jouez en mode aventure par limage de Nitro Oxide parce que lorsque lon effectue un saut avec Oxide, lon voit lombre dun kart ordinaire. Aussi ce code fait planter le jeu à plusieurs endroits dans le jeu tel que lorsque lécran de sélection du personnage apparaît (dans tous les modes de jeu) et aussi lorsque vous quittez la place du château en mode aventure.
Je joues avec la version NTSC [U] du jeu et le code que jai utilisé pour lessayer est 80086E84 000F. Vous devez avoir sauvegardé votre partie dans la place du château, sinon le jeu va planter. Crash Team Racing - Nitro Oxide in Adventure Mode](https://i.ytimg.com/vi/swFZNHKrFKo/mqdefault.jpg)

![Crash Bandicoot The Wrath Of Cortex Hacked : Unused Beta Level No. 2 - Removed AirShip Level
[January 2013 update]
The hidden and unused flight level of Crash Bandicoot: The Wrath of Cortex accessible (I believe) by two ways or methods, Data-Swapping Method and Code Hacking Method.
Using Data-Swapping Method : This Video
Using Code-Hacking Method : http://www.youtube.com/watch?v=6rck4n9ZZ38
-English-
I play with the NTSC version of the game and I used no codes like Action Replay, GameShark, etc. For this video, I have modded the level 2 (Tornado Alley) of the final version of this game for do it with the Crashs AirPlane. I did not remove the tornado generators because I want to be able to get the cristal and complete the level.
-Français-
Une présentation dun des niveaux retirés/inutilisés du jeu Crash Bandicoot 4: The Wrath Of Cortex sur PlayStation 2. Je joues avec la version NTSC de ce jeu et je nai pas utiliser de codes Action Replay, GameShark, etc. pour voir cet élément qui na pas vu le jour dans la version finale du jeu. Pour cette vidéo, jai modifié le deuxième niveau du jeu final (Tornado Alley) afin davoir lavion de Crash puisque je savait que ce niveau retiré allait en être un aérien. Je nai pas été capable denlever les générateurs de tornades, mais, au moins, le niveau se termine avec le cristal à la fin. Crash Bandicoot The Wrath Of Cortex Hacked : Unused Beta Level No. 2 - Removed AirShip Level](https://i.ytimg.com/vi/vS-Ky4_RRW4/mqdefault.jpg)


![Crash Team Racing - Hot Air Skyway OST [Prototype & Release Mix]
Note : The fist soundtrack you hear in this video, 00:10 - 03:12 is the final product. Other soundtracks are different versions of Hot Air Skyway, including original console prototype version and extracted RAW MIDI.
After ten years on this channel, here is a new Crash Bandicoot related video!
Hot Air Skyway from CTR, along with Rock it & Pack Attack from Crash Bandicoot 2 and Knight Time from Crash Bandicoot : The Wrath of Cortex are ones of my favorites soundtracks from the serie. Hot Air Skyway being my first favorite Crash Bandicoot sountrack I fell in love with mostly 20 years ago when I played CTR for the first time.
Recently, I found out that theres an extended version of Hot Air Skyway, called Pre-console that has been released by composer Josh Mancell. It includes an additional 28 seconds segment that consists mostly of the fist loop plus an instrument called the Cortexs Trumpet. Pre-Console music consists of music before instruments get stripped down, in this case, for the Playstation 1. CTR pre-console music sound great, but I always prefered original console music.
More recently, I joined the CTR-Tools (software used in this video) official Discord server and someone there told me that the original full length Hot Air Skyway is still here in one of some leaked CTR prototype builds. Okay, so I decided to take a look at this prototype build and I found out that the prototype Hot Air Skyway console version doesnt sounds like the release build console one. Some improvements have been made in the release version, especially in the first loop (compare 03:29 with 05:02). Also, the ripped version quality I found on The Cutting Room Floor is quite lower than what we can find in other video game music websites for the release version.
So, nothing really complicated for this video, we are trying to assemble the cut part of the prototype version while keeping the improvements made to the release one.
List of Hot Air Skyway versions you will hear in this video :
[ 00:10 - 03:12 ] Prototype & Release Mix
[ 03:12 - 04:44 ] Prototype
[ 04:45 - 05:50 ] Release
[ 05:50 - 07:22 ] Prototype, MIDI
[ 07:23 - 07:34 ] Cortexs Trumpet, cut part. Crash Team Racing - Hot Air Skyway OST [Prototype & Release Mix]](https://i.ytimg.com/vi/y1oiQLOJnN8/mqdefault.jpg)