Originally Posted by seamus517

All was good on my JB iPad 2, I went looking for a cellular data metering app, found one on Cydia (can't recall the name, it was the one with free trial then a few bucks to buy) installed it, then it prompted to reboot. After rebooting, the lock page came up fine, but the home screen looks very different, (the logos spaced differently and not all ), and when swiping to the left to the search page, an iPhone keyboard comes up. I fear I may have installed an iPhone only app.

Worst of all, when I click on any app, the screen switches for a half a second, then freezes, then the iPad reboots. This happens on every app I've tried, including Cydia.

I just bought this last week so I don't have my SHSH blobs to do a 4.3.3 restore.

Am I screwed? Is restoring to iOS 5 the only way out?

Hi,I also having this issue after update Cydia software yesterday.it alway reboot....reboot...and I make decision to restore the FW4.3.3 after that back to reinstall JB.now I still confuse what is the problem after update Cydia app...

Unfortunately I did not...I am brand new to Apple and JBing, but nobody to blame but myself here. I had started reading about openSSH...about the only thing I knew was not to keep the default password...but was trying to learn more before taking the plunge. I thought I was on the safe side by not putting something on before completely understanding it. (Something I should have done before upgrading the mobile substrate and installing that stupid data counter app!) If we are graced with an iPad 2 JB for iOS 5, I won't make that same mistake of not having openSSH installed. Is there a good primer where I can read everything I need to know for next time? What else should I have installed?

So given my choices of restoring and losing JB and the world's most expensive paperweight, I went with the former. At least I had iOS 5 to go to...if my only choice was 4.3.5, I would really be kicking myself. On the bright side, I am now an EXPERT on getting my iPad into DFU mode...

I ran into an issue when I was restoring and wanted to share it here for anyone else having the same problem.

I got iTunes to recognize that it was an iPad in recovery mode, clicked on restore & upgrade, but during the "verification" kept getting an unnumbered error saying "Free ipad software update server could not be contacted or is temporarily unavailable" and was banging my head into the wall trying to figure out what was going on. I tried lots of different things, unDFUing and reDFUing, rebooting, system restore to an earlier point, disabling my firewall (since it seemed the problem occurred when trying to connect to the Apple server) and eventually found the issue in my HOSTS file. The last line read

74.208.10.249 gs.apple.com

so it was trying to conect to the Cydia Apple-spoofing servers when I needed it to connect to the real Apple servers.

So I put a # in front of that line (I imagine deleting it would have worked too) , and after that it worked like a charm.

Hope this can help somebody stuck in the same position.

Originally Posted by f4780y

Do you have OpenSSH installed by any chance?bout

If so you can force SafeMode from the command line by using a tool such as Putty from your PC.

enter the following command:

touch /var/mobile/Library/Preferences/com.saurik.mobilesubstrate.dat

then respring (which you can force by clicking any icon).

That will force safemode and allow you to launch Cydia and remove the offending app. And remember to double check details when you install new apps in the future. Make sure it is iPad compatible. You get into all sorts of trouble installing old iPhone apps!

Seems like several others were having the same issue, so it may not be related to the Data Counter app as I previously suspected.

From what I read it appears that an update to the mobile substrate is what is causing this issue, and maybe only on iPad 2s.

Originally Posted by seamus517

Seems like several others were having the same issue, so it may not be related to the Data Counter app as I previously suspected.

From what I read it appears that an update to the mobile substrate is what is causing this issue, and maybe only on iPad 2s.

I agree