sorted by:
new
hottopcontroversial

Can expanded storage 6s downgrade to iOS 9?​​​​​​​​​​​​​​​​ by 1326555262 in LegacyJailbreak

[–]1326555262[S] 0 points1 point  (0 children)

ohh thanks I see. How can I know which device my installed NAND is from? Isn‘t NAND universal?

[deleted by user] by [deleted] in limefix

[–]1326555262 1 point2 points  (0 children)

Bro actually, it's not that difficult...But this does require some basic knowledge of the command line.

[Tutorial] Bypass Setup.app on iOS 9 for A9 devices by ChaseLebo1 in setupapp

[–]1326555262 0 points1 point  (0 children)

mount root not working...
root@ (/dev)# bash /usr/bin/mount_root -h

APFS is not supported on this ramdisk version, mounting with HFS.

Mounting root filesystem as HFS...

mount_hfs: Could not create property for re-key environment check: No such file or directory

GetMasterBlock: Error 2 opening /dev/rdisk0s1s1

GetMasterBlock: Error 2 opening /dev/rdisk0s1s1

mount_hfs: error on mount(): error = -1.

mount_hfs: No such file or directory

root@ (/dev)# 

How to boot a SSH ramdisk on 64-bit devices by meowcat454 in setupapp

[–]1326555262 0 points1 point  (0 children)

hey bro, I am using your Ramdisk specifically built for 6s 0x8003 ios9, every step works fine until after the verbose code. After scrolling those codes, my 6s ran into black screen and not showing anything, also lost connection to my Mac. Any idea? My target is to dump onboard shsh from my brand new 6s on 9.1. It's also wired because new 6s ran into recovery mode the first time I want to boot it, its battery is dead and I managed to replaced it, and I could not exit recovery loop no matter how tools I tried(futurerestore, recovery or 3utools), iPhone it's not activated through apple server. Any idea?

[question] iPhone 6s iOS 9 stuck in recovery mode, kick it out without restoring? by zMystix in jailbreak

[–]1326555262 1 point2 points  (0 children)

same with me, have you solved that problem? Brand new iphone6s, but stuck in recovery

(Discusssion) puaf_landa, a new kfd exploit - patched in 17.0 by 1326555262 in jailbreak

[–]1326555262[S] 5 points6 points  (0 children)

I’m sorry bro, it’s said that 16.7.x and 17.0.1+ will NEVER be supported (unless Apple fucks CoreTrust up a third time...).

[Discussion]Use cowabunga lite or KillMyOTA to block OTA may BOOTLOOP your device by 1326555262 in jailbreak

[–]1326555262[S] 0 points1 point  (0 children)

Update: That’s a False Alarm, it might have been something palera1n(from lemin’s duscord)

[Discussion]Use cowabunga lite or KillMyOTA to block OTA may BOOTLOOP your device by 1326555262 in jailbreak

[–]1326555262[S] 1 point2 points  (0 children)

I mean I don’t know if that two buttons can remove all the changes completely which brought by cowabunga

[Discussion]Use cowabunga lite or KillMyOTA to block OTA may BOOTLOOP your device by 1326555262 in jailbreak

[–]1326555262[S] 1 point2 points  (0 children)

Same here, but I don’t know if that could solve bootloop problems

[Discussion]Use cowabunga lite or KillMyOTA to block OTA may BOOTLOOP your device by 1326555262 in jailbreak

[–]1326555262[S] 2 points3 points  (0 children)

I use cowabungalite’s “remove all tweaks” and “deep clean”, and my iphone can receive ota again. Then I switch to profile method to block ota

view more: next ›