wow - what an ordeal - I feel for you. Had gone through similar digital warfare at some point, just not with Navigon. I doubt you are or will be the only one, so you can at least feel good about sharing your insights.
But before you give up completely.. have you tried [Only registered and activated users can see links. Click Here To Register...] yet (the Google Docs page might need 30 secs or so to generate)? It's fairly recent and does accept the most recent new maps, too.
Before you install it, make sure you remove all other Navigon completely (force stop, delete cache, delete data, uninstall).
Let us know hot it goes. Good news hopefully, finally. Fingers crossed, thumbs up.
18th September 2017, 08:30 AM
Craigs
Thanks, but this file version is in my archive already; so I am quite sure I have tried it as well, with no luck.
Since my real dilemma is with the generic serial number (and all tested tools failing to 'fix' it) I am now pursuing methods to alter it manually.
I am aware that this is totally OFF TOPIC here; yet I want to share my current findings, for those few who have this damn '123456789ABCDEF' issue.
The most promising approach appears to be an ADB command sequence that I dug up somewhere.
Albeit I do not understand its rather cryptic 'presentation'. A clean step-by-step command sequence would sure help.
If anyone can point me in the proper direction (best site to ask, or a complete script to use), please let me know, thanks!
This is what is supposed to create a different Android device S/N in any case:
"
adb shell
su
mount -o remount,rw /system
vi /system/etc/install-recovery.sh
# edit, save and exit
mount -o reount, ro /system
And here comes the line to add to /system/etc/install-recovery.sh to make the magic happen:
echo -n NEWSERIAL123 > /sys/class/android_usb/android0/iSerial
"
I assume that the 'edit' means to enter the special "echo" line in the install-recovery.sh file?
I may need to swallow more "Tongkat Ali" pills to develop the balls for hacking into the recovery area...
21st September 2017, 01:35 AM
gpspowrluvr
LOL right on, Tongkat Ali wll do .. ;)
If I were you, before more hacking, I'd do a full backup via TWRP or alike, wipe all, restore stock firmware ROM, and see if either the cra**ed Amazon or this one works steadily. If so then it might make sense to apply a more compatible custom ROM.
21st September 2017, 08:25 AM
Craigs
One of the various 'changer' tools allowed for a successful change of the Android_ID (not S/N, mind you). Of course with no impact on the Navigon app, as it really relies on the S/N, which is oddly frozen on my device.
I do have the TWRP backup, and besides the root everything else is 'stock' as there is very little activity around this fake tablet from Voyo (sold as 6.0 with 1.5GHz and 5Ah, in reality a crappy API 22 device with 1.3GHz and 4Ah battery). Russians hacked it somehow and even tinker with a Android 7.0 update, but I really do not want to mess with it that much. 250 apps are running just fine, just no Navigon at all.
Maybe I can find some help at XDA where I will officially ask for a method to fix a "frozen" serial number for good, if on the fly each time I boot this thing, whatever.
It is my utter belief that a unique S/N will cure my problem, and most likely future similar issues as well.
Until then I am swallowing pills...
Thanks for the continued support and ideas.