iPhone reset Stuck?

Skription

New Member
Jun 28, 2015
13
3
3
#1
Hello everyone, I have decided to jailbreak my iPhone because I wanted customization. I gotten a few errors but I decided to reset everything.

It's been about 10 minutes and it still not done.

I am thinking that it was I had a lot of space taken up.
 
Dec 15, 2008
5,386
340
83
28
Pensacola, FL
#2
What is iTunes showing or telling you? Are you still in the process of restoring your iPhone if that's what you did? Are you now on iOS 8.3?

What were the error codes that it was giving you?

If you are referring to Taig Jailbreak error codes, make sure you are on iTunes 12.0.1 and make sure you are using Taig 2.1.3.

If you get to the point where iTunes won't recognize your device, you'll need to put it into recovery mode to force restore.
  1. Turn off your device and leave it off.
  2. Plug in your device's USB cable to a computer with iTunes.
  3. Hold down the Home button on your device as you connect the USB cable. Keep holding down the Home button until you see the Connect to iTunes screen
  4. When you see this screen, release the Home button. If you don't see this screen, try steps 1 through 3 again.
https://support.apple.com/en-us/HT201263
 

Skription

New Member
Jun 28, 2015
13
3
3
#3
What is iTunes showing or telling you? Are you still in the process of restoring your iPhone if that's what you did? Are you now on iOS 8.3?

What were the error codes that it was giving you?

If you get to the point where iTunes won't recognize your device, you'll need to put it into recovery mode to force restore.
  1. Turn off your device and leave it off.
  2. Plug in your device's USB cable to a computer with iTunes.
  3. Hold down the Home button on your device as you connect the USB cable. Keep holding down the Home button until you see the Connect to iTunes screen
  4. When you see this screen, release the Home button. If you don't see this screen, try steps 1 through 3 again.
I'm restoring it now. Would it be wise to jailbreak it now?
 
Dec 15, 2008
5,386
340
83
28
Pensacola, FL
#4
I'm restoring it now. Would it be wise to jailbreak it now?
Which iPhone are you using?

Were the error codes in iTunes or the jailbreak process? You can attempt to jailbreak once your fully restored on iOS 8.3. Taig 2.1.3 is now out and has fixed bugs and is better stability.
 

Skription

New Member
Jun 28, 2015
13
3
3
#5
Were the error codes in iTunes or the jailbreak process? You can attempt to jailbreak once your fully restored on iOS 8.3. Taig 2.1.3 is now out and has fixed bugs and is better stability.
There is no error codes.
 

Skription

New Member
Jun 28, 2015
13
3
3
#6
Which iPhone or other device are you using?

Were the error codes in iTunes or the jailbreak process? You can attempt to jailbreak once your fully restored on iOS 8.3. Taig 2.1.3 is now out and has fixed bugs and is better stability.
Apologies for double posting but... I had this error code when I tried to install a tweak.

Sub-process /usr/bin/dpkg returned an error code (2)
 
Dec 15, 2008
5,386
340
83
28
Pensacola, FL
#7
There is no error codes.
Alright. Taig supports iPhone 6, iPhone 6 Plus, iPhone 5s, iPhone 5c, iPhone 5, iPhone 4S. You shouldn't have an issue jailbreaking as long as your on iOS 8.3 and iTunes version 12.0.1 or below 12.1. Be aware though it may get stuck at 20%, at least for many people it did. Other percentages can also take a little while.
 
Dec 15, 2008
5,386
340
83
28
Pensacola, FL
#8
Apologies for double posting but... I had this error code when I tried to install a tweak.

Sub-process /usr/bin/dpkg returned an error code (2)
Solution to sub-process /usr/bin/dpkg returned an error code:

  1. Get your way to the file and directory structure of your iPhone (through SSH or iFile or Mobile ..)
  2. Look for the /var/lib/dpkg/ directory
  3. You should be able to find the following files: available, availble-old, status, status-old
  4. Rename "available" to "available-bak"
  5. Rename "status" to "status-bak"
  6. Rename "available-old" to "available"
  7. Rename "status-old" to "status"
  8. Start Cydia , make sure that you allow Cydia to load completely first (just to be on the safe side ), try to install some apps.
http://wikitechsolutions.com/189/pr...process-usr-bin-dpkg-returned-an-error-code-2

Mind you this was for iOS 7.

*Not ALL tweaks etc are working yet on 8.3.*
 

Skription

New Member
Jun 28, 2015
13
3
3
#9
Solution to sub-process /usr/bin/dpkg returned an error code:

  1. Get your way to the file and directory structure of your iPhone (through SSH or iFile or Mobile ..)
  2. Look for the /var/lib/dpkg/ directory
  3. You should be able to find the following files: available, availble-old, status, status-old
  4. Rename "available" to "available-bak"
  5. Rename "status" to "status-bak"
  6. Rename "available-old" to "available"
  7. Rename "status-old" to "status"
  8. Start Cydia , make sure that you allow Cydia to load completely first (just to be on the safe side ), try to install some apps.

Mind you this was for iOS 7.

*Not ALL tweaks etc are working yet on 8.3.*
Can't install iFile.
 
Dec 15, 2008
5,386
340
83
28
Pensacola, FL
#10
Can't install iFile.
I'm going to wait for a moderator or someone else to help you, but let me ask this first. How did you jailbreak? Taig is available here. http://www.taig.com/en/ and is available currently only for Windows. Are you on iOS 8.3? I would assume so if you restored as it puts you on latest iOS.
 

Skription

New Member
Jun 28, 2015
13
3
3
#11
I'm going to wait for a moderator or someone else to help you, but let me ask this first. How did you jailbreak? Taig is available here. [censored 4 posts] and is available currently only for Windows. Are you on iOS 8.3? I would assume so if you restored as it puts you on latest iOS.
Yes, I'm on iOS 8.3
 

Europa

Moderator
Senior Moderator
Dec 12, 2008
28,365
5,507
113
Utah
#16
I was wondering if the OP had solved the problem or not. That would give us a better idea of whether or not to leave threads open.
I think Chris likes to keep them open regardless if the OP solves the problem or not just in case other people who are having a similar problem find this thread and want to post in it.
 

chris

Administrator
Administrator
Jun 10, 2006
11,813
1,779
113
Long Island, NY
#17
I think Chris likes to keep them open regardless if the OP solves the problem or not just in case other people who are having a similar problem find this thread and want to post in it.
Correct. By leaving it open, it allows for the next person with a similar issue to jump into the discussion. I'd rather have a single complete, living thread than 10 smaller threads on a similar topic.