app can't find the consolidated.db file

[thieu]

Hi Peter, thanks for creating this program!
I ran it and it didn't find the file. Here's what the feedback looks like. Any suggestions?
Matthieu

https://picasaweb.google.com/111395399298419104452/20Avr2011?authkey=Gv1sRgCPSZ34an84G8oAE&feat=directlink

[ryanprayogo]

Same problem here.

[kerinin]

My guess is that you're encrypting your backups. I had the same error, tried removing backup encryption, and now it works.

[loganlinn]

It was not able to find my consolidated.db file either. However, my iPhone was configured to encrypt backups. I disabled the encryption, did a backup, but was still unable to read it. I have a CDMA iPhone

I there are backups in my Backups folder and I can confirm there is a consolidated.db file in my latest backup.

[ryanprayogo]

Removing the encryption seems to solve the problem for me.

[4gra]

You'll get this message if there's any sort of failure reading the database. For instance you'll also see it if you try running this against an iPod Touch backup, since wifi log reading is disabled by default and iPods have no cell-based data.

In this case just modify iPhoneTrackingAppDelegate.m:155 as instructed.

I suppose I should add that, as the author rightly notes, wifi tracking is "dodgy". Doesn't mean it's not interesting in itself, though...

[Mallinanga]

i have disabled itunes backup alltogether so this probably won't work for me.
so i was wondering.. is it possible to make a command line switch or sth that will load a directly ssh transfered consolidated.db?

[doughsay]

I have a similar request to Mallinanga. It would be nice if there was some way to directly specify the location of the consolidated.db file. With my jailbroken phone I just used scp to get the file but can't tell iPhoneTracker to open it.

[Mallinanga]

there's a fork from pajp (https://github.com/pajp/iPhoneTracker) that has a commit where if the app fails to load the database from the itunes backup, it tries to load it directly from Desktop

BIG thanks to petewarden for this app, as well as to all other users forking this project and adding useful features!

[dustMason]

4gra's solution fixed the problem for me. I guess that means my phone hasn't been tracking cell location information? my map reflects only my wifi use. i can't decide if i'm reassured or disappointed ;)

[compguy99]

I don't have encryption enabled and I'm still unable "to find consolidated.db"... anybody have a solve for this?

[petewarden]

Sorry about that. There are several possible reasons that file loading might
fail:

• Your backups might be encrypted
• There might be no valid backups on that machine
• There may not be enough data collected
• You could have a phone that's still running iOS 3

I'm not quite sure what's up in your case though.

cheers,
Pete

On Wed, Apr 20, 2011 at 9:12 AM, thieu <
reply@reply.github.com>wrote:

Hi Peter, thanks for creating this program!
I ran it and it didn't find the file. Here's what the feedback looks like.
Any suggestions?
Matthieu

https://picasaweb.google.com/111395399298419104452/20Avr2011?authkey=Gv1sRgCPSZ34an84G8oAE&feat=directlink

Reply to this email directly or view it on GitHub:
#1

[ghost]

The tool doesn't work on Verizon iPhone without some very minor changes.
Apparently, for Verizon, actually specifically for CDMA networks, 'consolidated.db' has a new table called 'CdmaCellLocation' in addition to 'CellLocation'. The function 'tryToLoadLocationDB' will return NO, unless you change the queries line to include @"SELECT * FROM CdmaCellLocation". After that change, I was able to access location data.

[Cnie]

How do you remove backup encryption if you have lost your iPhone

[traceywashere]

is this app dead now?? it used to work .. and now, it's not .. i'm getting the same 'can't locate consolidated.db' file - i have an at&t phone, not jail broke ... my backup is not encrypted. i even tried encrypting, creating backup, then decrypting ... but still no joy.
did apple put out some other stealth "fix" that killed it?? i really liked how it worked ...

[4gra]

@traceywashere The iOS 4.3.3 update prevents location data being stored to backups, so you'll no longer be able to use the app on to retrieve even the limited (from 4.3.3 onwards) location data on the device. I wouldn't call it a 'stealth' update since it was the main announced purpose of the update, but still, I agree, it seemed like a nice way to get hold of some fascinating data in a way that you could control.