Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Brandonjr36

macrumors 68000
Original poster
Sep 12, 2016
1,624
563
Joplin
im wanting to jailbreak my X but I don’t want to risk bricking it. If I go ahead and jailbreak it and something like that happens is there away to unbrick it? Sorry about the stupid questions. This will be my first time jailbreaking anything...
 
Anything is possible with an X.

First backup anything you consider important. Do the computer iTunes backup and the iCloud backup.

Read the instructions twice so there is no misunderstanding.

Download the actual pristine jailbreak from the original author. You download from elsewhere expect nothing but headaches afterwards.

Jailbreak, expect a lot of Apple software to break because they check to see if the phone was jailbroken.

Expect your phone to get sick.

That’s it.

I hope you have a backup phone because a lot of tge code in jailbroken apps are beta and will act strangely if you are using a ios beta.
 
im wanting to jailbreak my X but I don’t want to risk bricking it. If I go ahead and jailbreak it and something like that happens is there away to unbrick it? Sorry about the stupid questions. This will be my first time jailbreaking anything...
It can happen, if you try really, really hard. I suggest a sledgehammer.

This is not 2007 where an 80+ series of steps and arcane hardware can render your device screwed. If anything happens, a DFU mode restore will take care of it.
[doublepost=1516627995][/doublepost]
Anything is possible with an X.

First backup anything you consider important. Do the computer iTunes backup and the iCloud backup.

Read the instructions twice so there is no misunderstanding.

Download the actual pristine jailbreak from the original author. You download from elsewhere expect nothing but headaches afterwards.

Jailbreak, expect a lot of Apple software to break because they check to see if the phone was jailbroken.

Expect your phone to get sick.

That’s it.

I hope you have a backup phone because a lot of tge code in jailbroken apps are beta and will act strangely if you are using a ios beta.
Ahh…the jailbreak hater type rears it's head!

First, yes. Anything is possible. Unlikely, but possible. Second, you do actually suggest a good thing. A backup. But then the rest of your post derails into anti-jailbreak rhetoric.

First off, there is more than one tweak that that will cloak jailbreaking. And usually it's banking apps that have a problem.

Your phone is not going to get sick - unless you put it into a spot to be sick by being dumb with it. Shady repos, pirated tweaks, going around to suspicious websites, etc.

Jailbreaking in and of itself does not make your phone "sick".

As far as beta code, there are a lot of tweaks that are NOT in beta. You're just applying a generalization here.
 
As there is no Cydia and no substrate at the moment, there is no up to date cloaking for the jailbreak either.
Not only banking apps use jailbreak detection, also media platforms such as DirectTV, games etc.
Just like jailbreaking itself, cloaking is a cat and mouse game where app makers update there apps to break cloaks.

As the jailbreak is still hardly out in the wild some hickups are expected and many tweaks don't work and need updating.

That also means that if you do try apps it might endup going in a loop requiring a DFU restore which means going to latest iOS and losing the ability to jailbreak.

At the moment I advise against jailbreaking for newbies, just be patient and let the tools update and work out the problems.

@eyoungren... we have 'crossed swords' before on the forum, I appreciate your inputs but I miss the caution in your advise to the newbies, when I was more active here I always pointed that out, I love jailbreaking but it has drawbacks and risks.
 
im wanting to jailbreak my X but I don’t want to risk bricking it. If I go ahead and jailbreak it and something like that happens is there away to unbrick it? Sorry about the stupid questions. This will be my first time jailbreaking anything...

Yes, yes it is. As to unbrick it, that will depend on what happened.
 
Yes, yes it is. As to unbrick it, that will depend on what happened.
Again. This is not 2007. Hell, none of the jailbreaks for later iPhones (including the X) are even fully untethered!

Unless you are trying VERY hard to brick the damn thing it's not going to happen.

Perhaps however, there is a misunderstanding of the word "brick" when it applies to a device. The word literally means a brick. You can do nothing. The device responds to zero input. It does not turn on the screen, it does not flash the Apple logo, it doesn't do anything at all. That's a brick.

Lately, the definition has been redefined by people who lazily apply it to mean a boot loop or a glitch or something similar. That is NOT a brick!

As long as you can enter DFU mode and recover the device, it is not bricked. And again, to get there you have to be trying extremely hard to screw it up.

It is possible, but it is not anywhere near probable.
 
  • Like
Reactions: rugmankc
Again. This is not 2007. Hell, none of the jailbreaks for later iPhones (including the X) are even fully untethered!

Unless you are trying VERY hard to brick the damn thing it's not going to happen.

Perhaps however, there is a misunderstanding of the word "brick" when it applies to a device. The word literally means a brick. You can do nothing. The device responds to zero input. It does not turn on the screen, it does not flash the Apple logo, it doesn't do anything at all. That's a brick.

Lately, the definition has been redefined by people who lazily apply it to mean a boot loop or a glitch or something similar. That is NOT a brick!

As long as you can enter DFU mode and recover the device, it is not bricked. And again, to get there you have to be trying extremely hard to screw it up.

It is possible, but it is not anywhere near probable.

You really need to evaluate jail breaking. Although it’s hard to do, the risk is there. You are writing into the OS new code to bypass Apple’s walled garden.

Not talking of the risk is simply (for lack of another word) risky behavior.
 
You really need to evaluate jail breaking. Although it’s hard to do, the risk is there. You are writing into the OS new code to bypass Apple’s walled garden.

Not talking of the risk is simply (for lack of another word) risky behavior.
Sigh.

There is risk. I do not deny risk. I never said I did. Read back. I said bricking was possible - just not likely.

Today's modern jailbreaks are not like it was 10 years ago.

As far as re-evaluating jailbreaking…no. I've been doing this since 2011 with iOS 5. My current iPhone has been stable on a 9.0.2 jailbreak since October 2015. I don't see anything that is going to prompt me to stop - except switching to Android later this year.
 
Well the message I am trying to convey is not coming across, that could of course be in the sender :)

An experienced JBer probably can get out of a 'brick' situation, but I have seen plenty of posts here of people that are even unable to get in to DFU, that makes it a hard brick for them and they might have to seek external advice, costing them money and time.

What is obvious for you might not be obvious for others, so I always kept that in mind when advising people on stuff like this.

All current available JBs for iPhone X are in beta, so no it is not easy and there is risk

From the LiberIOS website:

And yes, Code injection works, but CYDIA WILL NOT BE SUPPORTED. EVER. So please don't ask.

From the Electra JB website...doesn't sound easy to me...and then it probably is not easy...


Beta 6-5 (Current):
  1. Fix a regression in beta 6-4 that would cause launchd to run out of file descriptors
Beta 6-4 (Current):
Download: GitHub
SHA1: 1e6c8e767593f1d2ec15ef55b7b4a918df156341
Mirror: Mega

  1. Don't make jailbreakd rely on pidlistuptrs bug (thanks stek29)
  2. log dylib load errors in SBInject (thanks stek29)
  3. Clean up launchd payloads (thanks stek29)
  4. Load dylibs alphabetically from SBInject (thanks c0ldra1n)
  5. Check for jailbreakd start before reloading backboardd
  6. Make rejailbreaking significantly faster
Beta 6-3:
Download: GitHub
SHA1: 500e468b4852e980f16125c00f99fa9403f6eba0
Mirror: Mega

  1. Use host special port #4 to get tfp0 in jailbreakd (thanks n_triangle_dev)
  2. Add jailbreakd as a launchd service so it gets restarted if it dies (thanks n_triangle_dev)
Beta 6-2:
Download: GitHub
SHA1: f99a632ab0afffb168f920ed4c31c5a72ca123b7
Mirror: Mega

  1. Fix kernel memory leak in entitlement injector
Beta 6:
Download: GitHub
SHA1: 9e44c896abce6c835c45435d428426105e44857e
Mirror: Mega

  1. Add a working launchctl for loading launch daemons (thanks nullpixel)
  2. Load dropbear as a launch daemon & fix zombie process issue (thanks nullpixel)
  3. Set kernel task as host special port #4 (thanks stek29)
Beta 5:
Download: GitHub
SHA1: c0bc029cee9c16cf41a38d59884f41f39d85f610
Mirror: Mega

  1. Fix an issue in the substrate shim where substitute could crash if tweaks tried hooking nonexistent selectors
  2. Fix an issue with the dylib loader dragging UIKit (and all its tweaks) into every single daemon
  3. Make jailbreakd more robust with input struct size check enforcement
Beta 4-2:
Download: GitHub
SHA1: b7c01ce241c7b7fc594b850fb122a425e2e4c59a
Mirror: Mega

  1. Fix a symlink that would prevent some substrate extensions from working with libsubstitute
Beta 4:
Download: GitHub
SHA1: 8394694bb879de9a13d740d1c7ea773a398c5fbf
Mirror: Mega

  1. Disable NVRAM patching as it still appears to be unstable
  2. Make amfid patch more reliable so that more dylibs can be run properly
  3. Add a "shim" so existing substrate tweaks can use libsubstitute without modifications
Beta 3-3:
Download: GitHub
SHA1: 5f2b2531bd9cd8bcf116c0535505063d643a70b3
Mirror: Mega

  1. Fix the NVRAM patching crashing due to the memory page being unmapped (thanks Siguza)
Beta 3-2:
Download: GitHub
SHA1: 21fddbbd852179460589a41de52b6dc2461fab6f
Mirror: Mega

  1. Don't unlock NVRAM variables due to the patch crashing some devices.
Beta 3
Download: GitHub
SHA1: fd51e33cd3e46dc18636f5ce6a2a77a341b1a676
Mirror: Mega

  1. Unlock all NVRAM variables (including setting boot-nonce) [thanks stek29]
  2. Add support for binaries with SHA1 hashes (so existing dylibs work fine, but executables will need the entitlement) [thanks stek29]
  3. Clean up some garbage files that were present from previous build (yay macOS resource forks and .DS_Store)
  4. Hopefully fix the app icon not displaying on iPhones
  5. Significantly speed up the rejailbreak process

Beta 2:
Download: GitHub
SHA1: ef06cfacdb6e038c6269b2f4f0dc9f45e42a234b
Mirror: Mega

  1. Fix Anemone not reognizing themes
  2. Fix black screen when jailbreaking with tweaks enabled

Beta 1:
Download: GitHub
SHA1: 302a084fac30fab8d356fb33beb47ba9ed88c6fd
Mirror: Mega

  1. Initial Release


Important Information
  • Cydia, DPKG and APT are NOT included
  • GNU CoreUtilities are included
  • Dropbear, SCP and an SFTP server are running on ports 22 and 2222
  • Tweaks are installed in /bootstrap/Library/SBInject
  • Themes are installed in /bootstrap/Library/Themes
  • PreferenceLoader is configured to check /bootstrap/Library
  • Tweaks that crash SpringBoard will cause the device to respring into Safe Mode
  • All binaries must be signed using either ldid, ldid2, or jtool
  • Executables must be signed with the platform-application entitlement
  • Binaries and libraries should be installed in /bootstrap/usr/
  • An uninstall script is available at /bootstrap/unjailbreak.sh
    (Note this will only uninstall Electra)
 
Well the message I am trying to convey is not coming across, that could of course be in the sender :)

An experienced JBer probably can get out of a 'brick' situation, but I have seen plenty of posts here of people that are even unable to get in to DFU, that makes it a hard brick for them and they might have to seek external advice, costing them money and time.

What is obvious for you might not be obvious for others, so I always kept that in mind when advising people on stuff like this.

All current available JBs for iPhone X are in beta, so no it is not easy and there is risk

From the LiberIOS website:

And yes, Code injection works, but CYDIA WILL NOT BE SUPPORTED. EVER. So please don't ask.

From the Electra JB website...doesn't sound easy to me...and then it probably is not easy...


Beta 6-5 (Current):
  1. Fix a regression in beta 6-4 that would cause launchd to run out of file descriptors
Beta 6-4 (Current):
Download: GitHub
SHA1: 1e6c8e767593f1d2ec15ef55b7b4a918df156341
Mirror: Mega

  1. Don't make jailbreakd rely on pidlistuptrs bug (thanks stek29)
  2. log dylib load errors in SBInject (thanks stek29)
  3. Clean up launchd payloads (thanks stek29)
  4. Load dylibs alphabetically from SBInject (thanks c0ldra1n)
  5. Check for jailbreakd start before reloading backboardd
  6. Make rejailbreaking significantly faster
Beta 6-3:
Download: GitHub
SHA1: 500e468b4852e980f16125c00f99fa9403f6eba0
Mirror: Mega

  1. Use host special port #4 to get tfp0 in jailbreakd (thanks n_triangle_dev)
  2. Add jailbreakd as a launchd service so it gets restarted if it dies (thanks n_triangle_dev)
Beta 6-2:
Download: GitHub
SHA1: f99a632ab0afffb168f920ed4c31c5a72ca123b7
Mirror: Mega

  1. Fix kernel memory leak in entitlement injector
Beta 6:
Download: GitHub
SHA1: 9e44c896abce6c835c45435d428426105e44857e
Mirror: Mega

  1. Add a working launchctl for loading launch daemons (thanks nullpixel)
  2. Load dropbear as a launch daemon & fix zombie process issue (thanks nullpixel)
  3. Set kernel task as host special port #4 (thanks stek29)
Beta 5:
Download: GitHub
SHA1: c0bc029cee9c16cf41a38d59884f41f39d85f610
Mirror: Mega

  1. Fix an issue in the substrate shim where substitute could crash if tweaks tried hooking nonexistent selectors
  2. Fix an issue with the dylib loader dragging UIKit (and all its tweaks) into every single daemon
  3. Make jailbreakd more robust with input struct size check enforcement
Beta 4-2:
Download: GitHub
SHA1: b7c01ce241c7b7fc594b850fb122a425e2e4c59a
Mirror: Mega

  1. Fix a symlink that would prevent some substrate extensions from working with libsubstitute
Beta 4:
Download: GitHub
SHA1: 8394694bb879de9a13d740d1c7ea773a398c5fbf
Mirror: Mega

  1. Disable NVRAM patching as it still appears to be unstable
  2. Make amfid patch more reliable so that more dylibs can be run properly
  3. Add a "shim" so existing substrate tweaks can use libsubstitute without modifications
Beta 3-3:
Download: GitHub
SHA1: 5f2b2531bd9cd8bcf116c0535505063d643a70b3
Mirror: Mega

  1. Fix the NVRAM patching crashing due to the memory page being unmapped (thanks Siguza)
Beta 3-2:
Download: GitHub
SHA1: 21fddbbd852179460589a41de52b6dc2461fab6f
Mirror: Mega

  1. Don't unlock NVRAM variables due to the patch crashing some devices.
Beta 3
Download: GitHub
SHA1: fd51e33cd3e46dc18636f5ce6a2a77a341b1a676
Mirror: Mega

  1. Unlock all NVRAM variables (including setting boot-nonce) [thanks stek29]
  2. Add support for binaries with SHA1 hashes (so existing dylibs work fine, but executables will need the entitlement) [thanks stek29]
  3. Clean up some garbage files that were present from previous build (yay macOS resource forks and .DS_Store)
  4. Hopefully fix the app icon not displaying on iPhones
  5. Significantly speed up the rejailbreak process

Beta 2:
Download: GitHub
SHA1: ef06cfacdb6e038c6269b2f4f0dc9f45e42a234b
Mirror: Mega

  1. Fix Anemone not reognizing themes
  2. Fix black screen when jailbreaking with tweaks enabled

Beta 1:
Download: GitHub
SHA1: 302a084fac30fab8d356fb33beb47ba9ed88c6fd
Mirror: Mega

  1. Initial Release


Important Information
  • Cydia, DPKG and APT are NOT included
  • GNU CoreUtilities are included
  • Dropbear, SCP and an SFTP server are running on ports 22 and 2222
  • Tweaks are installed in /bootstrap/Library/SBInject
  • Themes are installed in /bootstrap/Library/Themes
  • PreferenceLoader is configured to check /bootstrap/Library
  • Tweaks that crash SpringBoard will cause the device to respring into Safe Mode
  • All binaries must be signed using either ldid, ldid2, or jtool
  • Executables must be signed with the platform-application entitlement
  • Binaries and libraries should be installed in /bootstrap/usr/
  • An uninstall script is available at /bootstrap/unjailbreak.sh
    (Note this will only uninstall Electra)
I’m gonna wait for cydia.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.