You may have heard that blizzard released their mobile authenticator for android via the android market.
Now the thing i was wondering is where serial is stored.
In the java emulator it was stored in a xxxx.db file, and in iphone in an xml file,
correct me if i'm wrong though.
Code:
<?xml version="1.0" encoding="utf-8"?>
<Serial>US-1234-5678-9123</Serial>
<Token>AQIDBAUGBwgJCgsMDQ4PEBESExQ=</Token>
<TimeDifference>-631</TimeDifference>
</Authenticator>
or this is perhaps an xml file to compile it for iphone/touch,
anyway, there is (or has to be) a way to change the serial , i've been looking in every xml or db file on my G2 but no succes yet, perhaps anyone else have found something?
I've encountered some difficulties with using the Blizzard Mobile Authenticator on my rooted handset. Seems it treats mine differently to a non-rooted handset and can be unusable. I've reported the problems on the official WoW forums here.
Regarding changing the serial code, why is this ever necessary? You can view it through the applications controls should you ever need to look it up. And you can always replace the authenticator on your account.
high class problem... i dont know it
jokeyrhyme said:
Regarding changing the serial code, why is this ever necessary? You can view it through the applications controls should you ever need to look it up. And you can always replace the authenticator on your account.
Click to expand...
Click to collapse
Haha, I answered my own question yesterday. Forgot to unlink my phone from my account before wiping it for a ROM update, and had to call Blizzard for help. It's lucky I had my original serial code written down. I can now see the value in being able to cause a fresh authenticator to behave like an older one.
This is something that has been talked about on another thread over at http://forum.xda-developers.com/showthread.php?t=557862
But from what I have been able to get, the data is stored in the file:
/data/data/com.blizzard.bma/shared_prefs/com.blizzard.bma.AUTH_STORE.xml
Now, how the token file is encoded... I can't say. Haven't gotten to that part yet.
jokeyrhyme said:
Haha, I answered my own question yesterday. Forgot to unlink my phone from my account before wiping it for a ROM update, and had to call Blizzard for help. It's lucky I had my original serial code written down. I can now see the value in being able to cause a fresh authenticator to behave like an older one.
Click to expand...
Click to collapse
dont mean to bring up a super old thread, but i couldnt find any answers (the post linked here shows how to read the serial from file, but not how to make it persistant or change it to something else) (sorry if its preferred to make a new thread to ask the question, seems like every forum prefers a different method, and this one seemed to be pretty spot on for what i was wondering)
I wanna try out different roms but keep the serial persistant. I could on my iphone by backing up the authenticator in itunes.
but even backing up app+data in titanium back up leaves me with a different serial.
Is there any way to get a backup with a persistant serial in it? I really dont want to leave my account unsecured, I dont want to have to carry around an extra keychain but im not going to deattach and reattach the authenticator every time i want to flash a rom.
bisby said:
dont mean to bring up a super old thread, but i couldnt find any answers (the post linked here shows how to read the serial from file, but not how to make it persistant or change it to something else) (sorry if its preferred to make a new thread to ask the question, seems like every forum prefers a different method, and this one seemed to be pretty spot on for what i was wondering)
I wanna try out different roms but keep the serial persistant. I could on my iphone by backing up the authenticator in itunes.
but even backing up app+data in titanium back up leaves me with a different serial.
Is there any way to get a backup with a persistant serial in it? I really dont want to leave my account unsecured, I dont want to have to carry around an extra keychain but im not going to deattach and reattach the authenticator every time i want to flash a rom.
Click to expand...
Click to collapse
iìll try to see if after 1+ year something changed and finally we can have an answer..
im in same condition.. id love to use mobile autenticator on android on my sgs2 BUT im kinda flashing roms kernels and testing every week different roms..
was hoping in titanium bkup.. but seems they wrot aint workin.. sooooooo any suggegstions?
Related
Hello guys,
Since 3 days now I can't start any purshased app (only see the loading screen then close itself) and I can't buy any app on marketplace, even free apps, always get 80004005 error...
I really don't know wt* is going, I don't have touched my registry (ok just the device name for testing but I set it back to OMNIA7).
Only sideloaded apps works. :/
I already tried to resynch the Live account but don't solve.
Anyone have an idea ?
Thanks.
Changing the device name is one of those NO SERIOUSLY DON'T MESS WITH THIS registry values - I thought the handful of places that ever recommended doing so had put up warning to that effect a while ago, but maybe not. It appears to break the DRM scheme the marketplace uses.
As for things to change... I assume you've tried rebooting the phone already? Also, make sure the registry value is exactly what it used to be, case sensitive and so forth.
In worst case, a hard reset will completley fix it. Registry changes are, fortunately, just in the Flash storage and are wiped in a hard reset.
Yeah.. I did a backup and reseted the phone, now it works.
And I lost all my SMS one more time.
I really wish there was a good way to back those up. It's difficult to extract and restore the SMS store.
Hi ninjy,
this is a problem of the marketplace at the moment.
I got many emails from users that have this problem with my app Week View.
I wrote something about it on my blog: http://www.hannesbiribauer.com/wordpress/?p=800
The problem is also disussed in the Ms answers forum and there is a thread for it in the WPDevFeedback Forum: https://wpdev.uservoice.com/forums/110705-dev-platform/suggestions/7168298-provide-fix-for-c101a7d1-when-updating-80004005-w
greetings,
Hannes
Broke the glass on my Titan and getting a replacement today. Getting the software back on is no problem and I really don't have any data to worry about since it's up on Skydrive.
But, is there anyway to save my text messages and restore them and the groups I have set up?
What else am I missing?
Thanks,
Rick
there's an sms back up tool in the app development forum.
as far as groups, i don't think theres a way to save them.
svtfmook said:
there's an sms back up tool in the app development forum.
as far as groups, i don't think theres a way to save them.
Click to expand...
Click to collapse
I'll go and search for it...
I've seen posts where people unlock their phones or load a particular Rom and use Zune to backup their phones. I haven't seen a post that actually describes how to do that. Not sure it applies here but after a while I am going to try and unlock my phone and try a couple of Rom's.
you can use the zune back up tools, but, i don't think any gen2 devices really have full support with roms and imaging tools.
svtfmook said:
you can use the zune back up tools, but, i don't think any gen2 devices really have full support with roms and imaging tools.
Click to expand...
Click to collapse
I must admit, I was pretty good on the WM platform but on WP and Zune, I am a newbie. I don't see where Zune will do a backup and like you said, there isn't much support for it which I interpret into, back it up is good but restoring is a whole other issue? Correct?
Gotta ask too, the signature you use. Do you still race? I am in my 50's now and raced locally into my 30's so it's been a while! The the part of your user ID that states SVT, any chance it references Ford vehicles?
The Zune backup image is tied to the hardware. You can't backup one phone and restore to a different phone.
Aphasaic2002 said:
The Zune backup image is tied to the hardware. You can't backup one phone and restore to a different phone.
Click to expand...
Click to collapse
Real world, people's phones are going to break and be replaced and in my case, with the exact same phone and model. Tools should be available to make this an easy task to complete. Not as an afterthought but as part of the base system.
Why take a happy customer and just tick the guy off when you can't replace all the data in a few easy steps.
Rickgig said:
Real world, people's phones are going to break and be replaced and in my case, with the exact same phone and model. Tools should be available to make this an easy task to complete. Not as an afterthought but as part of the base system.
Why take a happy customer and just tick the guy off when you can't replace all the data in a few easy steps.
Click to expand...
Click to collapse
Tell me about it. Apple and Android had backup/restore ability since day 1 - all smartphones should! Now with iOS5 Apple allow users to do a full backup and restore via iCloud over wifi; no computer needed.
WP7 is ridiculously behind - it's like Microsoft thinks our data isn't important to us? Anyway you can vote for this feature here:
http://windowsphone.uservoice.com/f...suggestions/suggestions/1549673-device-backup
There are ways to backup text messages, but it requires fully unlocking the device, which is not possible on the Titan yet.
If you have the tools to do it, replacing the touchscreen on your broken Titan with the one on the replacement would be the best way to keep your data.
Howdy (and apologies ahead of time if this is a dup, I _did_ search, didn't find anything),
Is it just me or did application specific passwords break with Lollipop? Googled a bit and couldn't find any details. I just see postings stating that 2fa works now, but I don't see how that negates the need for app specific passwords.
I know 2fa is now supported but I'm a bit concerned to use my normal password as I'm not sure if it's stored in any way. Anyone know of any links that explain what exactly is stored and how the auth is persisted across reboots? Maybe I'm misunderstanding, but I thought that if my device was lost, with app passwords I could revoke the device without changing my main password.
The other issue is, since I'm using 2fa with the google auth app on this phone I wouldn't even be able to setup if I wiped this phone (which I will need to). At least prevously I could login to my google account on my PC, create the app specific password and sign on that way.
- TIA for any info
I have just upgraded my Nexus 5 from 4.4.4 into 5.0.1 (I didn't install 5.0.0). What I did:
1. Factory reset on 4.4.4
2. Install system update into 5.0.1
2. Factory reset on 5.0.1
3. Application specific password NOT accepted on initial account setup on Nexus 5. I had to use my master password and code list because you can't read sms before account is added on the phone.
Is this really broken? I haven't found any info on this either.
Wow, someone else who was using this feature. That makes 2 of us at least. I guess that's why they removed it...? Yeah, unless I'm missing something it appears it's indeed broken.
The best part is this isn't really part of Android, but part of gapps; no way to report bugs for that (at least that I've found). Someone opened a bug against AOSP but they closed it as this stuff isn't part of AOSP:
{scheme}code.google.com/p/android/issues/detail?id=57863&can=1&q=app%20specific%20password&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
They suggested using the "google mobile help forum"; I guess this page links to it: {scheme}googlemobile.blogspot.com/2008/11/got-questions-try-new-google-mobile.html - following the link just gives an error "no group mobile found" or something similar.
All I could see to do was to post a response to their help page on signing in with app specific password to Play pointing out the inaccuracy of the article. I can't find that article anymore, it looks like it might've been removed? I received no response to that.
I can't imagine this being a very difficult feature to support, so I'm a little surprised it was removed. But hey, at least they added all sorts of eye candy and other crap I don't really care about.
I think this is a deal breaker for me. Unless I'm misunderstanding here, if someone were to acquire my phone and extract the password the key or whatever it's storing, they would then be able to access my account settings and take full ownership. If it only had the app specific password, I don't think that'd allow them to modify security settings. If it's tieing the key to the device, that's great but I still can't revoke it (doesn't show up in the app specific password page). Unacceptable (again, unless I'm misunderstanding something?).
Maybe it's time to start looking for alternatives. Wonder if any Maemo derivatives can run on the M8? It was miles ahead of Android in all departments except eye candy anyways...
I'll reply here if I see any more info - please do the same.
This is totally broken.
My company uses App Specific Passwords and I just updated my Droid Turbo to Lollipop.
After the update, everything worked fine. However, I started getting google play service errors and had to wipe.
Now I need to log in using my authenticator password instead of my app specific password.
Not good
dragonash said:
This is totally broken.
My company uses App Specific Passwords and I just updated my Droid Turbo to Lollipop.
After the update, everything worked fine. However, I started getting google play service errors and had to wipe.
Now I need to log in using my authenticator password instead of my app specific password.
Not good
Click to expand...
Click to collapse
Agreed. Quite unfortunate, but I can't find anyone outside of this thread and a few random posts that seem to actually care.
Thanks for confirmation that this is still a problem, btw. I'm still not sure if there's anyplace to even raise this to Google...
i just spent an hour trying to understand why this smart feature wasn't working on my new mobile with a stock andorid lollipop! at least i feel less lonely now...
i sent a feedback to google even if i don't think they'll reply.. i opened a ticket on AOSP website (Issue 189310) if you want to check their reply.. sorry but i can't post outside links
Hello everyone
i think this is my first post or one of the first on this forum, i'm a videogame modder(vice-boss at VStanced.com) who for fun also mods/dismounts/analyzes everything that slips in his hands(like, seriously every single thing). I have a semi-good knowledge of java and from some years i'm learning more and more about android, yet(as you can see) i still need help from time to time to figure out some stuff.
So, enough of presentation, time to talk about what i came here for.
I've been gifted a Cubot X9 some days ago, so the first thing i did was rooting(Kingroot -> Supersu-me) and applying a custom recovery(TWRP), i backed up rom and nvram with sp flash tool and the base rom(just rooted and recovery-ed) from recovery to make sure that in case i f**kd up something i could restore it without issues.
After that i restored all the additional apps and a couple gapps(Google Play Store, Google Play Services, Google Account Manager, Google Latin Keyboard) from a backup(Titanium Backup) of my old phone, a LG P990(Optimus Dual/X2/Star/Speed) and it all worked straight at first try. As soon as i finished restoring these i got myself a new recovery backup to prevent having to redo everything once again.
At the moment there are still 4 things that "bother" me, i've not been able to install Dialer, Contacts and Messaging apps from that same backup(they're a lot more comfortable than Cubot's original ones) because they just f**k up the whole thing, after a restart(either with or without cache/dalvik cleanup) System starts flickering/turning on and off and with it the background and the SIM control(it stop receiving any signal/recognizing the sim and wont allow me to open the sim selector/editor - for dual sim mode).
I've installed the first two apps(Dialer and Contacts) flawlessly with a root explorer(ES file explorer) and after deleting all odex files related to the old apps they worked well, cant say the same for Messaging(Mms.apk), it works but as soon as i press either on a received message, on the "new message" button or on "setup" it crashes to desktop.
Moreover, i'm not able to install the data backup(i'm mainly interested in contacts and messages but also the calls history) from Titanium Backup otherwise i'll get those issues i said above.
Mind both phones are 4.4.4 and so are their apps, on the LG P990 i had installed Slimroms' Slimkat but those apps i named should all be stock Google KitKat's ones(correct me if i'm wrong) and thus should work 1:1 on any 4.4.4 OS. Should.
You may ask me why i dont simply use google's backup system, so here's the answer, it is because i just dislike uploading my personal data and i honestly prefer figuring out how to do stuff manually.
I tried moving the *.db files from the old phone but they either cause to not show any messages(mmssms.db) or to not receive signal/not recognize the sim(telephony.db).
I have also installed an app called WAPPushManager.apk(com.android.smspush) from the old phone because i thought it could be somehow connected with the crash from clicking on the new message button but nothing changed.
So now i'm kinda lost, i have no clue if i'm missing to delete/add some files, or replace/add some apps.
Here's a few pics of the apps of which i'm speaking
I hope someone will be able to help me out on this, thanks a lot everyone for even bothering reading all this drama. hahaha
Also, yeah, you noticed well, i said that there are 4 things that bother me but i talked only about 3 things so here's the 4th:
this is more like a random question than a real issue or anything else(since i didnt even try yet). I would like to get the system bar and options/setup menu from the old phone(LG P990 Slimkat) to the new one(Cubot X9) but i have no clue if it is doable or not and what it eventually implies.
I'm looking forward for some magic to happen, thanks again
- BB93
Alright, i've been able to transfer all my contacts, calls and messages using an app called Super Backup, it did the trick quite quickly.
I still cant figure out why the Mms.apk wont work, i sent it over to a couple friends and all of them installed and used it right away. I am now almost sure the Cubot wont work correctly with it because it's dual-sim... in case there's anything(scripting wise) that can be done to make it work properly?
Well i kinda solved all my problems, for some reason that app just dont want to work on this phone, i downloaded another "kitkat 4.4 stock messaging app" from google play and it worked straight on... or almost, because for some reason that Super Backup program was messing my messages in a way that i had two threads for each person, one with sent and the other with received messages. Analyzing the *.xml file created by that tool i realized that it was using spaces between the numbers only for either received or sent messages(i didnt bother checking which of the two was it).
A basic example:
<sms address="+391234567890" time="22/gen/2016 09:18:58" date="1453450738028" type="1" body="THIS IS MY TEXT" read="1" service_center="+291234567890" name="" />
versus
<sms address="+39 123 45 67 890" time="22/gen/2016 09:18:58" date="1453450738028" type="1" body="THIS IS MY TEXT" read="1" service_center="+29 123 45 67 890" name="" />
Click to expand...
Click to collapse
It made so that the phone recognized those as different numbers and thus create the issue i said above.
I hope this little self-research thread will help someone else too in the future, thanks for reading.
- BB93
Bigg Boss93 said:
Well i kinda solved all my problems, for some reason that app just dont want to work on this phone, i downloaded another "kitkat 4.4 stock messaging app" from google play and it worked straight on... or almost, because for some reason that Super Backup program was messing my messages in a way that i had two threads for each person, one with sent and the other with received messages. Analyzing the *.xml file created by that tool i realized that it was using spaces between the numbers only for either received or sent messages(i didnt bother checking which of the two was it).
A basic example:
It made so that the phone recognized those as different numbers and thus create the issue i said above.
I hope this little self-research thread will help someone else too in the future, thanks for reading.
- BB93
Click to expand...
Click to collapse
Hi,
Thanks for using xda assist.
I see you've solved your problem. Thanks for being so thorough with your post. This should help others with the same problem. Enjoy the site :good:
Thread closed.
Hello,
I have a lg ls775 and under the user security certificates there is one called sprfw01. I have no idea why or what its for. Im on the sprint network. Is there a way i can inspect the cert or atleast figure out whats using it? Any info is greatly appreciated. Thnx guys!
Could this be from pairing my phone with some device ie. Smart watch or another phone?
Its actually under User credentials. Hope that can jog anyones memory as to what this may be.
I'm currently using the same phone as you and on the same carrier, and just noticed this user credential the other day as well. I didnt recognize it so I deleted it. I'm afraid I cant tell you if it really affected my device as it was already giving me some issues before I deleted the credential. At the time, and again today, I looked for the same answer as you and haven't found any additional information on it, so I can't be much help with exactly why it's there or what put it there.
However, I may be able to help put your mind at ease since I did happen to do a factory reset today and even though I deleted it before, it was back afterward. So my guess is that its not dangerous. (again, thats my opinion, hopefully someone can confirm if I am correct)
Some details to that lead me to think it's safe:
My LG G6 isn't rooted, and was not before the redo. (so technically nothing should have been able to reinstall it that was nefarious)
I didn't install any potentially shady apps when I did the factory reset ( at time of writing this, just a few big name apps from the play store, no random restored apks or anything like that).
I pulled my SD card out before the wipe and haven't put one back in yet, so that rules out something left over on there working itself back in somehow.
I allowed google to "restore" my most recent backup it made, but the most recent backup was AFTER I removed the credential so it shouldn't have been on there (google backups seems to restore very little anyway, and requests all backed up app downloads from the Play store) .
I have connected it to my home secured wifi.
No bluetooth connections yet.
No sharing to any devices or NFC usage, etc.
So from all of that, I believe it is either a Sprint thing, an LG UI thing, or something specific to the LG g6 model, and built into the factory settings. That's just my thoughts, but I thought maybe my experience might make you feel a little more at ease. Hopefully someone can reply with what the heck it actually is though, because little things like not being able to figure out the source of this drive me crazy even after all of that.
Just an update, I was looking through my LG V30+ and found the same credentials stored on this device too. No additional details on it's purpose were really gained from it though. Picture attached.
"User Credential" "sprfw01" also on LG ls 775
I saw the same thing and I searched "sprfw01" . I was wondering what it was. I also have this "User Credential" on an LG ls 775 on Sprint.
Passwords Saved Credential
I did some research into this and what I see is it's a credential from when you saved your passwords for an example unlock screen & any passwords like I have to specific websites.
Jusy my thoughts...
*Any good unlock or root for the ls993?