Subprocess pre removal script returned error exit status 1 cydia

Cydia Errors

Cydia.app includes many error messages that might not be easy to understand at first, including error messages that come directly from Debian APT.

Here are explanations for them and how to fix the problems!

Contents

Can’t find a source to download.

Can’t find a source to download.

Kill Cydia from appswitcher and refresh your sources.

Cydia error 255

Cydia error 255

This is caused by how the jailbreak app was signed, reboot and sign it with Xcode or Altserver

Cydia error 401 or 403 or 404 or 503

Cydia error 401 or 403 or 404 or 503

The repo that is hosting the package is offline, wait till is online again.

Cydia is not working after installing a package

Cydia is not working after installing a package

Use New Term 2 or ssh and dpkg -r fun.ignition.name of the package.

Cydia is «preparing filesystem» and won’t load

Cydia is «preparing filesystem» and won’t load

Create a file in your root folder called «.cydia_no_stash»

Could not get lock /var/lib/apt/lists/lock — open (35: Resource temporarily unavailable)

Could not get lock /var/lib/apt/lists/lock — open (35: Resource temporarily unavailable)

Cydia temporarily can’t refresh data because another program is already using a system component that Cydia needs. This error commonly happens if you’re also using another program that refreshes package data, such as Curiosa. To fix it, try rebooting. If that doesn’t help, you may need to uninstall Curiosa (and any other packages that do this).

Depends. » name of a package

Depends. » name of a package

Install the dependency.

Domain #10: -72000

Domain #10: -72000

Cydia ran into some kind of network problem. The usual cause of this error message is using packages that add tons of ad-blocking lines to your hosts file; uninstalling those packages should fix this error.

dpkg was interrupted, you must manually run ‘dpkg configure -a’ to correct the problem

dpkg was interrupted, you must manually run ‘dpkg configure -a’ to correct the problem

Cydia tries to fix this problem automatically. If this is the only error message displayed, you can ignore it and use Cydia normally.

Encountered a section with no Package: header
You may want to run apt-get update to correct these problems

One or more of your installed sources is set up incorrectly. You should be able to remove the problematic source by going to Sources and tapping «Edit» at top right. If you are not sure which one to remove, try removing all of them except the defaults (BigBoss, Cydia/Telesphoreo, Dev Team, ModMyi, and ZodTTD/MacCiti).

failed in buffer_write(fd) (7, ret=-1)

failed in buffer_write(fd) (7, ret=-1)
Sub-process /usr/bin/dpkg returned an error code (1)

There is not enough disk space (on the system or user partitions or both) for Cydia to install this package. Try removing some files first, such as large bootlogo or theme files; you may need to use iFile, OpenSSH, or some other way to access the filesystem. You can also check iFile’s trash folder (/var/mobile/Library/iFile/Trash). You can go to the Cydia homepage and tap «Storage Information» to check available space on both the system and user partitions.

Failed to fetch «name of a repo»

Failed to fetch «name of a repo»

The repository is down

GPG error: [repository] stable Release: The following signatures were invalid: BADSIG [number]

GPG error: [repository] stable Release: The following signatures were invalid: BADSIG [number]

This is a minor problem with a source. You did nothing wrong and can continue to use Cydia normally.

GPG error: [repository] stable Release: The following signatures were invalid: NODATA 1 NODATA 2

GPG error: [repository] stable Release: The following signatures were invalid: NODATA 1 NODATA 2
Failed to fetch [repository] Sub-process /bin/bzip2 returned an error code (2)
Some index files failed to download, they have been ignored, or old ones used instead.

One or more of your installed sources is temporarily or permanently unavailable. You may have typed in the wrong URL, the source may have shut down, the source may be broken, or the source may be denying your connection for some other reason. Try again later. If this problem keeps happening over many days, you can remove the problematic source by going to Sources and tapping «Edit» at top right.

Hash Sum mismatch

Hash Sum mismatch

The downloaded file does not match the file on the source’s server. This is often caused by a download getting interrupted before it finished, sometimes due to network problems and sometimes due to server problems.

If you get this for many packages, try a more reliable internet connection or try again later. If your internet connection is fine for downloading other packages, including from other repositories, there may be a problem with the package or the repository. It may be helpful to report this to the repository manager.

Host Unreachable

This may mean that your internet connection is not working, a source is not working, or something else is not working (such as the Cydia Store system). This is probably a temporary problem, so try again later.

HTTP/1.0 403

HTTP/1.0 403 This package is either paid or requires a paid package to function. If you paid: contact saurik@saurik.com for help. If not, purchase the original package.

If you get this error while trying to download a paid package you have already purchased, email saurik@saurik.com for help. If you are trying to download a paid package you have not purchased, buy it and then try downloading it again. If you are trying to download a free add-on to a paid package (for example, a package adding a new option to Color Keyboard), you have to purchase that paid package before you will be able to download this add-on.

HTTP/1.1 403 Forbidden

HTTP/1.1 403 Forbidden

Just turn off WiFi and use your cellular signal to bypasses this.

HTTP/1.1 404 Not Found

HTTP/1.1 404 Not Found

The repo is not online.

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

Something seems to be wrong with the source hosting this package. This is probably a temporary problem, so try again later.

I wasn’t able to locate file for the [package] package. This might mean you need to manually fix this package.

I wasn’t able to locate file for the [package] package. This might mean you need to manually fix this package.

This is a generic error that means something went wrong. This may happen if you try to install a package while fresh data is downloading from your repositories (the stage right before «Reloading Data»). Try going to the Changes tab, tapping «Refresh» at top left, waiting for data to finish downloading, waiting for Reloading Data to complete, and then installing this package again.

Internal error, No file name for.

Internal error, No file name for.

Kill Cydia from appswitcher and refresh your sources.

POSIX error: Operation Timed Out.

POSIX error: Operation Timed Out.
POSIX: Socket is not connected.
NetDB: Open nodename nor servname provided, or not known.

Cydia is working properly, but something is wrong with your device’s connection to one or more of your installed sources. Your internet connection may not be working properly, or the source may not be working properly. Check your internet connection and try again later.

Pre-dependency problem

install all the dependencies first and then the tweak.

Problem parsing dependency

Problem parsing dependency Pre-Depends or Problem parsing dependency Depends
Error occurred while processing [repository]
Problem with MergeList [file]
The package lists or status file could not be parsed or opened

One or more of your installed sources is set up incorrectly. (This is a problem with that source, not with Cydia.) You should be able to remove the problematic source by going to Sources and tapping «Edit» at top right.

Read-only file system

Read-only file system

In terminal/via SSH, try running the following:

su alpine (if u never changed it) fsck -f -n

Once done, reboot and re-run the jailbreak and it should work.

Size mismatch

The downloaded file does not match the file on the source’s server. This is often caused by a download getting interrupted before it finished, sometimes due to network problems and sometimes due to server problems.

If you get this for many packages, try a more reliable internet connection or try again later. If your internet connection is fine for downloading other packages, including from other repositories, there may be a problem with the package or the repository. It may be helpful to report this to the repository manager.

subprocess pre-removal script returned error exit status [number]

subprocess pre-removal script returned error exit status [number] or subprocess dpkg-deb —fsys-tarfile returned error exit status [number] or similar
Sub-process /usr/bin/dpkg returned an error code (1)

Something seems to be wrong with this package. Tap «Author» at the top of the package page and email the developer (and ideally the repository manager as well) to let them know about the problem and ask for help.

The packege index file are corrupted. No filename: field for: «name of a package»

The packege index file are corrupted. No filename: field for: «name of a package»

Remove the repo that is hosting that package

The package «name of the package» needs to be reinstalled, but i can’t find an archive for it.

The package «name of the package» needs to be reinstalled, but i can’t find an archive for it.

Use New Term 2 or ssh and run dpkg —remove —force-remove-reinstreq «name of the package» and then run dkpg —configure -a

trying to overwrite [file], which is also in package [package]

trying to overwrite [file], which is also in package [package]
Sub-process /usr/bin/dpkg returned an error code (1)

You are trying to install a new package that contains the same filenames as a package you already have installed, so you cannot install this new package. You can usually avoid this problem by avoiding (or uninstalling) illegally copied versions of packages.

Warning: parsing file (. ) missing maintainer

Warning: parsing file (. ) missing maintainer

This is safe to ignore. Pirated tweaks usually are the culprit to this issue.

Warning: Target Packages (Packages) is configured multiple times in.

Warning: Target Packages (Packages) is configured multiple times in.

You have a duplicate repo, follow the path and remove the duplicate repo.

Warning: Target Translation is configured multiple times in.

Warning: Target Translation is configured multiple times in.

You have a duplicate repo list, follow the path and remove the duplicate repo list.

Wow, you exceeded the number of package names this APT is capable of.

Wow, you exceeded the number of package names this APT is capable of.
Problem with MergeList [file]
The package lists or status file could not be parsed or opened.

This happens if you are using an old Cydia version (before 1.1.10) and have too many packages available from your installed sources. You will need to refresh your sources and update all relevant packages, so that you get the latest versions of Cydia and associated packages — but in order to do that, you’ll first need to fix this error. The error means that you have more than 65,535 packages available from your installed sources, and your old version of Cydia cannot handle that many. Go to Manage, tap Sources, tap «Edit» at top right, and remove some sources. Make sure to keep the default repositories (BigBoss, Cydia/Telesphoreo, ModMyi, and ZodTTD/MacCiti). If some sources don’t have a «remove» button when you try to remove them, that usually means they were installed as packages. Go to Manage, tap Packages, find the package with the source’s name, and uninstall that package. After removing a few extra sources, you should be able to refresh data without this error.

Источник

Thread: linux-image post-removal script subprocess returned error exit status 1

Thread Tools

Display

linux-image post-removal script subprocess returned error exit status 1

I have recently upgraded from 18.04 LTS to 20.04 LTS. During the upgrade, there were errors to do with removing an old kernel.
If I run Synaptic, and select Broken dependencies, there is one package listed: linux-image-4.15.0-117-generic
The linux-image is marked for complete removal and cannot be un-marked. If I Apply the changes, then the details windows has the output shown below.

Although I have used Ubuntu LTS releases for many years, they have always just worked and so I have little experience in fixing issues such as the one I have now.
In the output below I can see a number of errors, including «/etc/grub.d/25_custom_proxy: 3: /etc/grub.d/bin/grubcfg_proxy: not found» and «installed linux-image-4.15.0-117-generic package post-removal script subprocess returned error exit status 1». I am guessing that we can ignore the «cryptsetup: WARNING: Option ‘size’ missing in crypttab» error for now.

Can anyone suggest what I should do next? I have searched the forums for answers but haven’t found anything that works. If someone can point me to a relevant thread, I would appreciate that.

Cheers
Andrew Mc

Re: linux-image post-removal script subprocess returned error exit status 1

The directory /etc/grub.d/ contains files that are automatically executed when grub is updated. It contains a file named /etc/grub.d/25_custom_proxy (which doesn’t exist on a stock Ubuntu system), that in turn tries to execute /etc/grub.d/bin/grubcfg_proxy, which doesn’t exist.

Have you done anything to customise grub that may have put that 25_custom_proxy file there? It looks like it was put there by some tool and not properly removed before the upgrade. Can you find out to which package it belongs?

Источник

Thread: Error: subprocess installed post-removal script returned error exit status 1

Thread Tools

Display

Error: subprocess installed post-removal script returned error exit status 1

I can’t get any updates for my system and keep getting the errors shown below, and suggestions peeps?

E: linux-image-2.6.28-11-generic: subprocess installed post-removal script returned error exit status 1
E: linux-image-2.6.28-13-generic: subprocess installed post-removal script returned error exit status 1
E: linux-image-2.6.28-14-generic: subprocess installed post-removal script returned error exit status 1
E: linux-image-2.6.28-15-generic: subprocess installed post-removal script returned error exit status 1
E: linux-image-2.6.28-19-generic: subprocess installed post-removal script returned error exit status 1

Re: Error: subprocess installed post-removal script returned error exit status 1

Tried this in Update Manager, Synaptic, and Terminal — all give similar replies and the same error code?

Re: Error: subprocess installed post-removal script returned error exit status 1

full output of the terminal is:

if no-one knows how to fix this can anyone tell me how to unmark the old kernels for removal?

Re: Error: subprocess installed post-removal script returned error exit status 1

I’ve been trying to fix this for over two hours now, does anyone know how to sort it out?

Error: subprocess installed post-removal script returned error exit status 1

hi I’m having a problem with my system atm, could anyone help? my first post is: here, kind of makes sense to keep it in one place

Re: Error: subprocess installed post-removal script returned error exit status 1

Please keep to one thread per issue and feel free to bump it once per 24(ish) hours if no reply.

Re: Error: subprocess installed post-removal script returned error exit status 1

To remove old kernels, either use synaptic & search for «linux-image-2», mark the old ones for removal and click apply, or use Ubuntu Tweak which will remove them for you.

As for the problem you posted about. Try running these commands.

Last edited by Dutch70; April 21st, 2011 at 10:33 PM .

Re: Error: subprocess installed post-removal script returned error exit status 1

Hi, thanks for the reply, I tried your suggestions and have included the output from the terminal at the end of this post.

How I got in this trouble:
I was trying out themes for grub with http://ubuntuguide.net/decorate-grub. r-gui-for-burg that software and there was an option to clear old kernels, that’s how I got to where I am now.

From here all I want to do is get these packages either removed so my updates work again, or unmarked for removal so it doesn’t try to remove them before running updates, any further assistance would be greatly appreciated

Re: Error: subprocess installed post-removal script returned error exit status 1

Have you removed Burg? I’m really not sure, but if it’s settings. Try running these.

Last edited by Dutch70; April 22nd, 2011 at 01:42 AM .

Re: Error: subprocess installed post-removal script returned error exit status 1

Hi, tried those again, and it still comes up with the same output in the terminal.

also went into Synaptic Package manager and tried in there, whilst there I noticed that there are no linux-header-x-x-x for these linux-image packages and right clicking on the packages and selecting Properties -> Installed Files shows an empty box whereas with my other installed kernels it provides a very long list, think maybe these packages are gone already and the problem is that it can’t find the files to remove?

and burg is still on the system, it won’t let me install, upgrade or remove anything :S

where is the file that lists all the installed packages? and has it been in the same place since 8.04ish as that’s when i first installed ubuntu on this machine

Источник

Cydia Errors

Cydia.app includes many error messages that might not be easy to understand at first, including error messages that come directly from Debian APT.

Here are explanations for them and how to fix the problems!

Contents

Can’t find a source to download.

Can’t find a source to download.

Kill Cydia from appswitcher and refresh your sources.

Cydia error 255

Cydia error 255

This is caused by how the jailbreak app was signed, reboot and sign it with Xcode or Altserver

Cydia error 401 or 403 or 404 or 503

Cydia error 401 or 403 or 404 or 503

The repo that is hosting the package is offline, wait till is online again.

Cydia is not working after installing a package

Cydia is not working after installing a package

Use New Term 2 or ssh and dpkg -r fun.ignition.name of the package.

Cydia is «preparing filesystem» and won’t load

Cydia is «preparing filesystem» and won’t load

Create a file in your root folder called «.cydia_no_stash»

Could not get lock /var/lib/apt/lists/lock — open (35: Resource temporarily unavailable)

Could not get lock /var/lib/apt/lists/lock — open (35: Resource temporarily unavailable)

Cydia temporarily can’t refresh data because another program is already using a system component that Cydia needs. This error commonly happens if you’re also using another program that refreshes package data, such as Curiosa. To fix it, try rebooting. If that doesn’t help, you may need to uninstall Curiosa (and any other packages that do this).

Depends. » name of a package

Depends. » name of a package

Install the dependency.

Domain #10: -72000

Domain #10: -72000

Cydia ran into some kind of network problem. The usual cause of this error message is using packages that add tons of ad-blocking lines to your hosts file; uninstalling those packages should fix this error.

dpkg was interrupted, you must manually run ‘dpkg configure -a’ to correct the problem

dpkg was interrupted, you must manually run ‘dpkg configure -a’ to correct the problem

Cydia tries to fix this problem automatically. If this is the only error message displayed, you can ignore it and use Cydia normally.

Encountered a section with no Package: header

Encountered a section with no Package: header
You may want to run apt-get update to correct these problems

One or more of your installed sources is set up incorrectly. You should be able to remove the problematic source by going to Sources and tapping «Edit» at top right. If you are not sure which one to remove, try removing all of them except the defaults (BigBoss, Cydia/Telesphoreo, Dev Team, ModMyi, and ZodTTD/MacCiti).

failed in buffer_write(fd) (7, ret=-1)

failed in buffer_write(fd) (7, ret=-1)
Sub-process /usr/bin/dpkg returned an error code (1)

There is not enough disk space (on the system or user partitions or both) for Cydia to install this package. Try removing some files first, such as large bootlogo or theme files; you may need to use iFile, OpenSSH, or some other way to access the filesystem. You can also check iFile’s trash folder (/var/mobile/Library/iFile/Trash). You can go to the Cydia homepage and tap «Storage Information» to check available space on both the system and user partitions.

Failed to fetch «name of a repo»

Failed to fetch «name of a repo»

The repository is down

GPG error: [repository] stable Release: The following signatures were invalid: BADSIG [number]

GPG error: [repository] stable Release: The following signatures were invalid: BADSIG [number]

This is a minor problem with a source. You did nothing wrong and can continue to use Cydia normally.

GPG error: [repository] stable Release: The following signatures were invalid: NODATA 1 NODATA 2

GPG error: [repository] stable Release: The following signatures were invalid: NODATA 1 NODATA 2
Failed to fetch [repository] Sub-process /bin/bzip2 returned an error code (2)
Some index files failed to download, they have been ignored, or old ones used instead.

One or more of your installed sources is temporarily or permanently unavailable. You may have typed in the wrong URL, the source may have shut down, the source may be broken, or the source may be denying your connection for some other reason. Try again later. If this problem keeps happening over many days, you can remove the problematic source by going to Sources and tapping «Edit» at top right.

Hash Sum mismatch

Hash Sum mismatch

The downloaded file does not match the file on the source’s server. This is often caused by a download getting interrupted before it finished, sometimes due to network problems and sometimes due to server problems.

If you get this for many packages, try a more reliable internet connection or try again later. If your internet connection is fine for downloading other packages, including from other repositories, there may be a problem with the package or the repository. It may be helpful to report this to the repository manager.

Host Unreachable

This may mean that your internet connection is not working, a source is not working, or something else is not working (such as the Cydia Store system). This is probably a temporary problem, so try again later.

HTTP/1.0 403

HTTP/1.0 403 This package is either paid or requires a paid package to function. If you paid: contact saurik@saurik.com for help. If not, purchase the original package.

If you get this error while trying to download a paid package you have already purchased, email saurik@saurik.com for help. If you are trying to download a paid package you have not purchased, buy it and then try downloading it again. If you are trying to download a free add-on to a paid package (for example, a package adding a new option to Color Keyboard), you have to purchase that paid package before you will be able to download this add-on.

HTTP/1.1 403 Forbidden

HTTP/1.1 403 Forbidden

Just turn off WiFi and use your cellular signal to bypasses this.

HTTP/1.1 404 Not Found

HTTP/1.1 404 Not Found

The repo is not online.

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

Something seems to be wrong with the source hosting this package. This is probably a temporary problem, so try again later.

I wasn’t able to locate file for the [package] package. This might mean you need to manually fix this package.

I wasn’t able to locate file for the [package] package. This might mean you need to manually fix this package.

This is a generic error that means something went wrong. This may happen if you try to install a package while fresh data is downloading from your repositories (the stage right before «Reloading Data»). Try going to the Changes tab, tapping «Refresh» at top left, waiting for data to finish downloading, waiting for Reloading Data to complete, and then installing this package again.

Internal error, No file name for.

Internal error, No file name for.

Kill Cydia from appswitcher and refresh your sources.

POSIX error: Operation Timed Out.

POSIX error: Operation Timed Out.
POSIX: Socket is not connected.
NetDB: Open nodename nor servname provided, or not known.

Cydia is working properly, but something is wrong with your device’s connection to one or more of your installed sources. Your internet connection may not be working properly, or the source may not be working properly. Check your internet connection and try again later.

Pre-dependency problem

install all the dependencies first and then the tweak.

Problem parsing dependency

Problem parsing dependency Pre-Depends or Problem parsing dependency Depends
Error occurred while processing [repository]
Problem with MergeList [file]
The package lists or status file could not be parsed or opened

One or more of your installed sources is set up incorrectly. (This is a problem with that source, not with Cydia.) You should be able to remove the problematic source by going to Sources and tapping «Edit» at top right.

Read-only file system

Read-only file system

In terminal/via SSH, try running the following:

su alpine (if u never changed it) fsck -f -n

Once done, reboot and re-run the jailbreak and it should work.

Size mismatch

The downloaded file does not match the file on the source’s server. This is often caused by a download getting interrupted before it finished, sometimes due to network problems and sometimes due to server problems.

If you get this for many packages, try a more reliable internet connection or try again later. If your internet connection is fine for downloading other packages, including from other repositories, there may be a problem with the package or the repository. It may be helpful to report this to the repository manager.

subprocess pre-removal script returned error exit status [number]

subprocess pre-removal script returned error exit status [number] or subprocess dpkg-deb —fsys-tarfile returned error exit status [number] or similar
Sub-process /usr/bin/dpkg returned an error code (1)

Something seems to be wrong with this package. Tap «Author» at the top of the package page and email the developer (and ideally the repository manager as well) to let them know about the problem and ask for help.

The packege index file are corrupted. No filename: field for: «name of a package»

The packege index file are corrupted. No filename: field for: «name of a package»

Remove the repo that is hosting that package

The package «name of the package» needs to be reinstalled, but i can’t find an archive for it.

The package «name of the package» needs to be reinstalled, but i can’t find an archive for it.

Use New Term 2 or ssh and run dpkg —remove —force-remove-reinstreq «name of the package» and then run dkpg —configure -a

trying to overwrite [file], which is also in package [package]

trying to overwrite [file], which is also in package [package]
Sub-process /usr/bin/dpkg returned an error code (1)

You are trying to install a new package that contains the same filenames as a package you already have installed, so you cannot install this new package. You can usually avoid this problem by avoiding (or uninstalling) illegally copied versions of packages.

Warning: parsing file (. ) missing maintainer

Warning: parsing file (. ) missing maintainer

This is safe to ignore. Pirated tweaks usually are the culprit to this issue.

Warning: Target Packages (Packages) is configured multiple times in.

Warning: Target Packages (Packages) is configured multiple times in.

You have a duplicate repo, follow the path and remove the duplicate repo.

Warning: Target Translation is configured multiple times in.

Warning: Target Translation is configured multiple times in.

You have a duplicate repo list, follow the path and remove the duplicate repo list.

Wow, you exceeded the number of package names this APT is capable of.

Wow, you exceeded the number of package names this APT is capable of.
Problem with MergeList [file]
The package lists or status file could not be parsed or opened.

This happens if you are using an old Cydia version (before 1.1.10) and have too many packages available from your installed sources. You will need to refresh your sources and update all relevant packages, so that you get the latest versions of Cydia and associated packages — but in order to do that, you’ll first need to fix this error. The error means that you have more than 65,535 packages available from your installed sources, and your old version of Cydia cannot handle that many. Go to Manage, tap Sources, tap «Edit» at top right, and remove some sources. Make sure to keep the default repositories (BigBoss, Cydia/Telesphoreo, ModMyi, and ZodTTD/MacCiti). If some sources don’t have a «remove» button when you try to remove them, that usually means they were installed as packages. Go to Manage, tap Packages, find the package with the source’s name, and uninstall that package. After removing a few extra sources, you should be able to refresh data without this error.

Источник

Jailbreak Problems and Cydia Errors Super Thread

More options

Tabuu

So welcome to the jailbreak problems and Cydia errors super thread. Let’s get started with Cydia eh?
Most Cydia error messages mean there are problems with packages or sources you have installed, not bugs in Cydia, so you can resolve the errors yourself. A lot of errors can be solved by doing the following:

1. Open Cydia, go to Changes, tap Refresh on the top left, wait for data to download and reload (if this process takes a long time it’s fine), and then try installing a package.
2. If that does not fix it, try this: open Cydia, go to Manage and tap Sources (or on iPad just go to Sources), tap Edit, and remove any third-party repositories — make sure to leave the default repositories, which are BigBoss, Cydia/Telesphoreo, ModMyi, and ZodTTD/MacCiti (this is very important as these are some of the most important sources).
3. If that still does not help, try rebooting your device and opening Cydia again.

But there are some errors that need more specific troubleshooting, or you might want to skip that general-purpose process and jump to the specific problem. Here are explanations for several error messages (in alphabetical order for your ease of searching. or you can just type ctrl+f or cmd+f to find a specific error. up to you. ):

dpkg was interrupted, you must manually run ‘dpkg configure -a’ to correct the problem
Cydia tries to fix this problem automatically. If this is the only error message displayed, you can ignore it and use Cydia normally.
Encountered a section with no Package: header
You may want to run apt-get update to correct these problems

One or more of your installed sources is set up incorrectly. You should be able to remove the problematic source by going to Manage -> Sources on iPhone and iPod touch (or Sources on iPad) and tapping «Edit» at top right. If you are not sure which one to remove, try removing all of them except the defaults (Cydia/Telesphoreo, Dev Team, ModMyi, and ZodTTD/MacCiti). To run «apt-get update» you must download MobileTerminal (it is currently supported on iOS 6). Next you type the following commands in:

1. su (this puts the iDevice terminal into super user mode)
2. «password» (the original password is «alpine» without quotes, if you changed it then insert you password without the quotes)
3. apt-get update (just let it run until it is finished)

failed in buffer_write(fd) (7, ret=-1)
Sub-process /usr/bin/dpkg returned an error code (1)

There is not enough disk space (on the system or user partitions or both) for Cydia to install this package. Try removing some files first. On iPhone and iPod touch, you can go to Manage -> Storage to check available space on both the system and user partitions.

GPG error: [repository] stable Release: The following signatures were invalid: BADSIG [number]

This is a minor problem with a source. You did nothing wrong and can continue to use Cydia normally. Just come back and try again later and hopefully it will be fixed.

GPG error: [repository] stable Release: The following signatures were invalid: NODATA 1 NODATA 2
Failed to fetch [repository] Sub-process /bin/bzip2 returned an error code (2)
Some index files failed to download, they have been ignored, or old ones used instead.

One or more of your installed sources is temporarily or permanently unavailable. You may have typed in the wrong URL, the source may have shut down, the source may be broken, or the source may be denying your connection for some other reason. Try again later. If this problem keeps happening over many days, you can remove the problematic source by going to Manage -> Sources on iPhone and iPod touch (or Sources on iPad) and tapping «Edit» at top right.

Hash Sum mismatch

The downloaded file does not match the file on the source’s server. This is often caused by a download getting interrupted before it finished, sometimes due to network problems and sometimes due to server problems. Try installing this package again later.

This may mean that your internet connection is not working, a source is not working, or something else is not working (such as the Cydia Store system). This is probably a temporary problem, so try again later.

HTTP/1.0 403 This package is either paid or requires a paid package to function. If you paid: contact [email protected] for help. If not, purchase the original package.
If you get this error while trying to download a paid package you have already purchased, email [email protected] for help.

If you are trying to download a paid package you have not purchased, buy it and then try downloading it again. If you are trying to download a free add-on to a paid package (for example, a package adding a new option to Color Keyboard), you have to purchase that paid package before you will be able to download this add-on.

HTTP/1.1 500 Internal Server Error

Something seems to be wrong with the source hosting this package. This is probably a temporary problem, so try again later. It is sometimes caused with high server load.

I wasn’t able to locate file for the [package] package. This might mean you need to manually fix this package.

Something weird went wrong. Try going to the Changes tab, tapping «Refresh» at top left, waiting for data to finish downloading, and then installing this package again.

POSIX error: Operation Timed Out.
POSIX: Socket is not connected.
NetDB: Open nodename nor servname provided, or not known.

Cydia is working properly, but something is wrong with your device’s connection to one or more of your installed sources. Your internet connection may not be working properly, or the source may not be working properly. Check your internet connection and try again later.

Problem parsing dependency Pre-Depends or Problem parsing dependency Depends
Error occurred while processing [repository]
Problem with MergeList [file]
The package lists or status file could not be parsed or opened

One or more of your installed sources is set up incorrectly. (This is a problem with that source, not with Cydia.) You should be able to remove the problematic source by going to Manage -> Sources on iPhone and iPod touch (or Sources on iPad) and tapping «Edit» at top right.

subprocess pre-removal script returned error exit status [number] or subprocess dpkg-deb —fsys-tarfile returned error exit status [number] or similar
Sub-process /usr/bin/dpkg returned an error code (1)

Something seems to be wrong with this package. Tap «Author» at the top of the package page and email the developer (and ideally the repository manager as well) to let them know about the problem and ask for help.

trying to overwrite [file], which is also in package [package]
Sub-process /usr/bin/dpkg returned an error code (1)

You are trying to install a new package that contains the same filenames as a package you already have installed, so you cannot install this new package. You can usually avoid this problem by avoiding (or uninstalling) illegally copied versions of packages.

Wow, you exceeded the number of package names this APT is capable of.
Problem with MergeList [file]
The package lists or status file could not be parsed or opened.
You have more than 66,000 packages available from your installed sources, and Cydia cannot handle this many. Go to Manage -> Sources on iPhone and iPod touch (or Sources on iPad), tap «Edit» at top right, and remove some sources. It’s recommended to keep the stock repositories (BigBoss, Cydia/Telesphoreo, Dev Team, ModMyi and ZodTTD/MacCiti).
This error is no longer an issue with the new cydia update. Cydia now holds a few billion packages. which is more metadata than your device has storage for.

Error Couldn’t configure pre-depend dpkg for ncurses, probably a dependency cycle:

The common reason why you would get this error is because your version of cydia is outdated. In order to update cydia, all you have to do is re-jailbreak without restoring. yes I mean jailbreak an already jailbroken iDevice.
Some people have also had luck with simply rebooting their iDevice then letting cydia update it’s repositories.

POSIX error: Broken Pipe

This error is known to occur when the connection between your device and the server hosting the package is broken (aptly named eh?). Anyway, just like any other server connection problem, you simply have to try again later.

Could not open file /var/lib/dpkg/status — open (2: No such file or directory)

Please read this detailed tutorial on how to fix the problem.

Now then, for the jailbreak errors.

Auto Brightness Bugs
This is sometimes caused by a tweak or by a respring. It has happened a lot on my phone recently. The bug seems to come and go so you never know what will work for sure. You can try turning the auto brightness function off then on again, reboot your device, or both.

Stuck at Boot Screen
This seems to be a common problem with the new Evasi0n jailbreak. The fastest way to fix the problem is to hard restart the iDevice. To hard restart you simply hold the power and home buttons for about 5 seconds or until the screen goes black. The device will reboot and hopefully it will not be stuck. If it is, just try it a few more times. If it is still stuck then you will most likely have to restore your iDevice to factory settings and reapplying the jailbreak.
NOTE: For some reason with the Evasi0n jailbreak the boot time is unusually long. If you phone doesn’t boot up after three minutes then you are definitely stuck.

Problems with the stock Weather.app
There have been a lot of users complaining about the Weather.app file (the normal stock weather application) not working after using the Evasi0n jailbreak. By not working, I mean crashing. You must be patient for this to be fixed. Some of you may have the but while others don’t. Personally, I don’t have it on my iPhone 4S.

Cydia Applications Crashing
This could be caused by any number of things. The most common reason why applications crash after you install them through Cydia is that they simply are not compatible with the iOS you are running. For example, when my iPhone 4S was jailbroken on iOS 5.1.1, I was able to use eWiFi. Now, on iOS 6.1, I am unable to use eWiFi because it crashes every time I attempt to run the application. You can take two paths from here, you can uninstall the application and check on it later to see if it has been updated to work on the iOS you are running, or you can save the application and wait for Cydia to prompt you for an update. if one ever comes.

Random White Icon Show Up After Installing SBSettings
In order to fix this you simply open the SBSettings application, click the option for mobile substrate addons, and turn off «libhide». Your device will Respring after making this change so don’t panic.

Random Application Crashes
This can be caused by any number of things, most commonly though it is caused by lack of good memory allocation and out-dated cydia packages. There are a few things you can do in order to fix this. Make sure you go into cydia once or twice a week and make sure all your tweaks and applications are up-to-date. Ones that are not up-to-date, may be leaking memory causing more and more to be used up than is actually needed. There is a package on the cydia store named iCleaner. This app deletes all the temp files that are not needed or being used in order to speed up your device. Another important thing you can do is clean out the multitasking tray, this closes all applications running in the background. After you clean out the tray, you can either reboot or respring you iDevice. I recommend rebooting since it does a more thorough job.

Runtime Error info.plist Not Found
This is a semi-common error found while using the Cydia store application called Dreamboard. If you encounter this error, don’t panic, it is fixable. First what you will want to do is download the program called Redsn0w. You would download it from here (just scroll down to where it says Download Redsn0w then choose the one for your firmware in the drop-down window). Next, you will want to boot your iDevice in safe mode (this can be done with a springboard application or by holding the volume up buttom while turning on the iDevice). Next, you will want to go into Cydia and completely uninstall Dreamboard. After that, simply reboot your iDevice and you should be good to go. Feel free to download Dreamboard again, but make sure you download themes that are compatible with your iDevice and/or firmware.

I just resprang and all my apps have disappeared
This happens from time to time with certain springboard applications such as Atom and LowBatteryBanner. The fix is pretty easy, all you have to do is reboot your iDevice. If it doesn’t work after the first reboot, try it a couple more times.

My iDevice keeps forcing itself into safe mode
This happens because you have installed or updated a package that is damaged or incompatible with your firmware or iDevice. The simplest way to fix this is just to go in to cydia while you are in safe mode and remove the installed package. That will fix the problem 9/10 times. I highly suggest that you go through your installed package list once a week and do some cleaning. That way you don’t have to worry about overloading your iDevice with unneeded packages.

New Method to fix your iDevice

Yup, that’s right. Just recently a new method was made to fix most of your jailbreak problems. This method is called Semi-Restore. This method allows you to restore your iDevice to almost stock firmware while preserving your jailbreak. The Semi-Restore site is http://semi-restore.com/
please check it out, it’s incredibly helpful.

Warning: if you remove a package that is installed to cydia (such as package icon sets or cydia patches), it may damage the kernel and may force your iDevice in to an infiniboot. The only way to fix this is with a restore.

If I missed anything please let me know so I can update this post. You may post any bugs you have encountered at all throughout your experience with jailbreaking any iDevice. If you have a solution, please post that as well so that I can easily update the original post. If you don’t have a solution, then worry not, post anyway, and I will look for a solution.

Источник

Modded/Hacked App: 마계전기 DISGAEA RPG By Hong Kong Bao Chuan Software Technology Limited
Bundle ID: com.boltrend.disgaeakr
iTunes Store Link: https://apps.apple.com/kr/app/%EB%A7%88%EA%B3%84%EC%A0%84%EA%B8%B0-disgaea-rpg/id1632554348?uo=4

Mod Requirements:
— Jailbroken iPhone/iPad/iPod Touch.
— iGameGod / Filza / iMazing or any other file managers for iOS.
— Cydia Substrate, Substitute or libhooker depending on your jailbreak.
— PreferenceLoader (from Cydia, Sileo or Zebra).

Hack Features:
— x Dmg
— x Def

Non-Jailbroken & No Jailbreak required hack(s): https://iosgods.com/forum/79-no-jailbreak-section/
Modded Android APK(s): https://iosgods.com/forum/68-android-section/
For more fun, check out the Club(s): https://iosgods.com/clubs/

iOS Hack Download Link:

Hidden Content
Download Hack

Installation Instructions:
STEP 1: Download the .deb Cydia hack file from the link above. Use Safari/Google Chrome or other iOS browsers to download.
STEP 2: Once the file has downloaded, tap on it and then you will be prompted on whether you want to open the deb with iGameGod or copy it to Filza.
STEP 3: If necessary, tap on the downloaded file, and then, you will need to press ‘Install’ from the options on your screen.
STEP 4: Let iGameGod/Filza finish the cheat installation. Make sure it successfully installs, otherwise see the note below.
STEP 5: If the hack is a Mod Menu — which is usually the case nowadays — the cheat features can be toggled in-game. Some cheats have options that can be enabled from your iDevice settings.
STEP 6: Turn on the features you want and play the game. You may need to follow further instructions inside the hack’s popup in-game.

NOTE: If you have any questions or problems, read our Troubleshooting topic & Frequently Asked Questions & Answers topic. If you still haven’t found a solution, post your issue down below and we’ll do our best to help! If the hack does work for you, please post your feedback below and help out other fellow members that are encountering issues.

Credits:
— AlyssaX64

Cheat Video/Screenshots:

N/A