Don't know what I did...or when even...but I can no longer sideload apps to my Focus. The App Deployer gives an error stating it cannot connect to the device...make sure it is fully booted and plugged in to the PC. Problem is that it is. I have verified that it is fully unlocked...I can use sideloaded apps already on the phone and used Samsung Registry to go and verify the keys. I have been running the RTM and updated it today. I also updated my wifes LG Quantum today...she was still on NoDo. After updating her phone I tried sideloading and it said she was not unlocked so I went in and unlocked her phone and then it sideloaded as expected.
So long story there, does anybody have any ideas on what might be the issue.
Related
This morning I had 5 apps come up for update. Two of them updated fine. The last three stalled about mid-way through and then showed the attention required message. When I tap the the message I get "There is a problem completing your request. Try again later. Error Code: 8103010d
All three apps are demos, but the two that completed were as well. Googling the error code did not bring up anything useful.
Probably because mango is in beta and the apps haven't been fully updated to mango
Sent from my T9295 using XDA Windows Phone 7 App
jklier said:
This morning I had 5 apps come up for update. Two of them updated fine. The last three stalled about mid-way through and then showed the attention required message. When I tap the the message I get "There is a problem completing your request. Try again later. Error Code: 8103010d
All three apps are demos, but the two that completed were as well. Googling the error code did not bring up anything useful.
Click to expand...
Click to collapse
If had the same error yesterday with PES2011 (full version) and today with Turn by Turn Navigation. I managed to get the latest PES2011 by uninstalling and then downloading the complete new version again. Doesn't seem to work with TBT, since it's grayed out for some reason.
@nalgrim
It's most definitely an issue with the mango beta. But I'm very certain it's not by far related to apps not being updated for mango. None of the apps currently available on the marketplace is.
Turn by Turn was one of mine as well. I figured it had something to do for Mango but I'm just checking to see if there's a work around. Since updating to Mango I've had dozens of updates with no issues.
Not a big deal. I'm still enjoying Mango even as a beta version.
I found that when I tried updating certain apps over my data connection I had this (or at least I think it was this) issue. Updating over wifi seemed to fix it though.
Casey
Casey_boy said:
I found that when I tried updating certain apps over my data connection I had this (or at least I think it was this) issue. Updating over wifi seemed to fix it though.
Casey
Click to expand...
Click to collapse
I tried both, data and WiFi. None of them worked for me. At least not with TBT.
Same here. WIFI didn't make a difference.
I noticed that it's not the download that fails, but the installation. Download in Mango is always completed when the 50% mark is reached. After that the installation process starts. That's where the error occurs.
dkp1977 said:
I noticed that it's not the download that fails, but the installation. Download in Mango is always completed when the 50% mark is reached. After that the installation process starts. That's where the error occurs.
Click to expand...
Click to collapse
Someone who has figured out what to do? I got this problem today with hTC hub update.
I know this is an old thread but, I wanted to put a post here for people with this issue. I had a demo installed and I tried to buy the app and I got the 8103010d error(this is with a current version 8107 not just mango). I uninstalled the demo with the same error.
I went online and found a sideload version(a hacked version) of the app and installed it. Then I uninstalled it. I attempted to reinstall from the marketplace and it installed fine.
As I dont promote pirating software, it fixed my issue here, just make sure you delete the pirated software after attempting this.
DavidinCT said:
I know this is an old thread but, I wanted to put a post here for people with this issue. I had a demo installed and I tried to buy the app and I got the 8103010d error(this is with a current version 8107 not just mango). I uninstalled the demo with the same error.
I went online and found a sideload version(a hacked version) of the app and installed it. Then I uninstalled it. I attempted to reinstall from the marketplace and it installed fine.
As I dont promote pirating software, it fixed my issue here, just make sure you delete the pirated software after attempting this.
Click to expand...
Click to collapse
Well I think simply uninstalling the demo or whatever the old app is and then installing the new one should do the work. It did for me.
If anyone is able to help me, I would greatly appreciate it.
I installed Google Wallet (via this APK) when I first got my Verizon LTE GN a few weeks back. I've since used the app daily and it has worked perfectly, up until this evening.
Today, for the first time ever, I decided to unlock my bootloader in order to root my device--all of which went smoothly. I then re-downloaded the above GW APK (since unlocking wiped my device) but now when I launch the application, the screen stays at "Initializing your device - This may take a few minutes depending on your network connection." The application doesn't freeze (the circle continues to spin), but after 30 minutes of waiting, still, nothing has happened. I've tried reinstalling the APK but that does nothing. I have 4G connectivity and have tried over WiFi also.
I am running stock recovery, stock ROM, stock everything on 4.0.2. All I did was unlock the bootloader & root the device. I've done quite a bit of searching but have been unable to find a solution. Does anyone know what may be causing the issue or what I could do to fix it? I really enjoy using the application
I'm having a pretty similar problem.
CDMA Galaxy Nexus.
When I first got the phone, I downloaded the Google Wallet apk and it worked fine. Used it a few times out in the real world.
Today, used the wug unlock/root method, and installed a custom rom.
Though the rom feature log said it contained Google Wallet, it did not.
I redownloaded the original APK that I had used and it installed, but now I get this "Unfortunately wallet has stopped" message every time.
In fact, it comes up on the screen at random intrevals.
Not sure if there's anything I can do.
Do you guys have NFC enabled from the settings menu?
Also, did you try disabling and re-enabling NFC? It's different hardware, but after flashing one ROM I had to disable/re-enable GPS before it would work... worth a shot.
Hello,
I have a Samsung focus unlocked. Os version 7.10.8873.98 and can't deploy with Tom XAP installer like before.
Everything working, but giving me the error that I have a locked phone or zune not running.
It's not a big deal because everything was installed in the right row with other apps. But before, I didn't have this message and the apps started after install....
Didn't do any changes. Someone having the same issue and figure what happen?
thanks
So I tried doing the systemless root thing. I tried confirming that android pay would still work by removing my cards then attempting to re-add them and it failed. I tried undoing what I did by flashing stock recovery, boot, and system. Still a no-go. I tried running the flash-all.bat (i removed the "-w" so I would keep my data). Still can't add a card.
I resorted to running the flash-all.bat, build MDB08M, to be 100% stock. I STILL CANNOT add a card. The message has been the same every single time "Android Pay cannot be used - Google is unable to verify that your device or the software running on it is Android compatible"
Am I missing something? I don't understand how a 100% stock flash is not able to work.
If it makes you feel any better I've been running 100% stock since day 1 and tried using Android Pay for the first time today. Failed same as yours saying device or software couldn't be verified. I had originally set it up using my card that was already set up on my Google account. When this card didn't work I removed it and tried adding the card again manually. Couldn't even add a card. Tried rebooting several times and disabled developer options. Still not working.
I can select a card already on my google account, accept the terms, then the message pops up. Happens with two different cards associated with my account.
I'm fully stock, but unlocked bootloader.
Android pay used to work as recently as 4 days ago, but failed today with the error unable to verify.
Not willing to relock bootloader. Was there an update of Google play services that changed the way they check for modifications to include bootloader unlock?
I went back to complete stock relocked bootloader and Android paid don't work for me because chase bank stopped supporting Android pay so I went back to custom ROM
Just to note my bootloader is unlocked, otherwise I am 100% stock.
I manually tried updating Google play services to the latest version, but Android Pay gave me the same message but at a different point in the process - right after I clicked "Add a credit or debit card." I wasn't even able to see cards already associated with my account like before. I ended up uninstalling the update because it seemed to make things worse.
I just tried this app and it says I'm failing the SafetyNet check:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Same here. Completely stock 5x with nova. Had added a card, but wasn't working so I deleted it to try to re-add. No luck... Pretty annoying actually. I don't use it that often, but there have been several occasions I forgot my wallet going to the grocery store and paid with android pay cause it's all I had. Hope it gets fixed soon.
Looks like it is working all of a sudden. I was trying the safetynet checking app a few times a day... just tried now and it finally passed. Gave android pay a whirl and both cards were able to be added without issue. So apparently something happened on Google's end. Google play services is the same version now as it was when android pay failed to work.
I was failing the safetynet API yesterday. I still am.
I was also unable to pay with anything yesterday, but today I was able to add a card. Presumably it's partially fixed.
I went completely stock with relocked bootloader and STILL failed the test.
If it's working again, it's probably something wrong on Google's part. I'll try adding a card with systemless root
Ugh, what a headache, I ended up deleting everything for no reason.
Anyone else find it to be working now? I ran the safety net check last night and it passed. Tried adding my card and this time it worked. Big G must have fixed something on their end.
I ran remote erased on the phone because I thought I had lost it, but had later found it. I downloaded the SuperSU app to see if its still rooted, and it is not. So I ran an update check, and it throws an error saying 'The operating system on your device has been modified in an unauthorized way. Try downloading software updates using Smart Switch on your computer or visit a customer service center.' I tried updating with Smart Switch, but it fails with an 'unknown error'. Its last update was August 3, 2017 and TWRP 3.1.0-1_ashyx is still installed. I would very much prefer to get Android 8 on this phone.