Thread: NAVIGON Europe v5.9.0 patched

Thanks, an interesting observation about the TWO SIM cards!
Indeed I DO have two installed, albeit NOT online at the same time. Most of the time only WLAN is on, not the SIM cards.
Of course my tablet is rooted, as I explained with my XPrivacy 'identification' mods. I do have the Xposed framework and other goodies on board.
Also a few IMEI changer apps, but am not sure what I should enter, just another one? I quickly glanced at the version.xml file of Navigon and all looked OK to me (no "1234" or "1111" stuff inside).
Not that I am dependent on any navigation apps, but this stoic 'an error has occurred' is nagging me for years. I want to UNDERSTAND and also to HANDLE this weird issue on my phone and tablet.

This version of NAVIGON excellent works but not well kreknuta and only works when you are connected to the Internet and there is a problem to us and I need an APK that works without the Internet because here the story here if someone has version 5.90, which works without the Internet please to have him in the division

Update on my 'an error has occurred':
- the tablet had only ONE SIM card installed (but two slots)
- when ONLY activating the mobile data (WLAN off) Navigon complains about 'server connection error', this indicates that it does not 'see' the internet??
- when activating WLAN and optionally also the SIM the known problem 'an error has occurred' is displayed
- the tablet shows a reasonable IMEI number when checking
- the associated version.xml file contains really odd and old data (rev 5.9, different IMEI etc)
- entering my real IMEI in the version.xml file makes no difference, the error remains when starting the app

What I have NOT tried yet:
- swapping the SIM card to the other card slot
- adding a second SIM into the tablet and try either/both at the same time
- using IMEI fake apps (but WHAT to fake, what IMEI should I enter, the wrong one from the version.xml file?)

What does this cryptic and bland 'an error has occurred' really mean? It is NOT a connection issue, rather a 'verification' issue as far as I can tell by its behavior.

thank you best regards leon

no idea, sorry. You quoted the error in German, so maybe following [Only registered and activated users can see links. ] could help you.

I do know the German discussions about this message; in fact some of my solution attempts were based on their recommendations.
By chance I discovered a potential root cause, but am currently unable to 'repair' it:
not the IMEI may be the rejection reason, but the hardware SERIAL number, which is '123..EF'. Assuming that even the cracked versions do a SN match check, this may cause the decline of service and 'an error has occurred'. Most likely MANY devices report this common serial number and few apps seem to care for it.
Unfortunately I am too stupid to manage XPrivacy, as I have not found a way to inject a different or even random SN at that moment (I can block it, but that is of no help).
And the alternative and promising app 'DonkeyGuard' is not working at all, crashing right after every attempt to run it in the XPosed shell. There may be other tools to replace serial numbers on the fly.
I will pursue this attempt, still fighting for a solution and to boost of my ego... never give up!

I just installed both cracked versions, the one from this thread and the latest Amazon one, on my new Samsung Galaxy J5 dual-SIM, and as expected and stated by others, no IMEI issue. Only the Telekom Select Edition is IMEI sensitive.

If you think you're on the right track w/ faking a different serial number; good luck with that.

Also you might want to try and install the [Only registered and activated users can see links. ] just to see how that one behaves.

This is getting ridiculous:
- even the (hopefully functional) injection of a new IMEI and Serial Number with XPrivacy has not solved the issue
- installation of the free version worked, and it would start correctly multiple times, for ONE day. The following day I got the same 'An error has occurred' message...WTF?

I am now considering the cumbersome 'carefree package' method offered elsewhere. It is so complex and error prone that I really wanted to avoid it, yet what else could I possibly try? If even the official version downloaded from the Playstore is failing on day #2, this hack will probably fail as well.

The very last attempt is to use a brandnew SIM card, create a new Google identity with it, and then install the app once more.
I have no clue what this weird app is trying to verify and why it fails utterly for me, regardless what version I am trying to run.

My final verdict, after examining all my findings so far:
- the root cause of my (and apparantly just MY) problem is a fatal combination of two issues: Navigon relying on specific system IDs and my tablet unwilling to 'alter' its generic SN data.
- The S/N change app I tried reported 'success', but showed the old and wrong one ("123456789ABCDEF") after each restart anyway, a first suspicious hint
- the permission controller tool DonkeyGuard does install, but crashes whenever started without even showing a splash screen, apparently losing the battle against my Android 5.1; another suspicious hint that matches the first one.
- the XPrivacy tool allows to block these IDs (useless); when trying to alter and save the critical ones it will show the randomly generated fake numbers but will not store them. As soon as I peek into the 'Settings' after saving, IMEI and SN are shown as '0000' and 'DEFACE' again. So it most likely feeds the original IDs to Navigon each time it starts, causing the 'an error has occurred' reaction.
- even the installation of the free trial version of Navigon exposes the same issue, on day #2, after working fine on day #1 (so they seem to check the ID not right away)
That solidifies my assumption that all these tools basically fail for a similar reason; with different reactions.

Quintessentially this means that my rooted China tablet, despite running on stock API 22 (Lollipop_MR1), uses internal trickery to prevent any attempt of altering the system IDs, for whatever reason.
Maybe the flashing of a new image or other Android version could solve the problem? But I am not willing to take chances just for the installation of this f.cking navi app.

What appears to be really needed is a version of Navigon that either circumvents these ID checks at startup entirely. Or that creates a random S/N value at installation time, that will be used inside this app whenever it is started later. Only needed for folks with a generic SN '1234..DEF' AND a locked down system that does not allow for the faking of real numbers. A miniscule number of users would benefit, no modder will ever go that route - bummer..

So Navigon DID win this battle against me after all - I lost the war.
Yet they did not squeeze a dime out of me either; so I will leave the arena 'heads up' anyways!
I wonder if they would refund me in such a case, if I had purched this frigging application that cannot work due to stupid verification checks?!


Most likely the modded version offered here in this thread is OK for most other users, just not me.
Sorry for the intrusion.