Just got my G2x yesterday, activated it to T-Mo and I haven't yet rooted/ROM'd (mainly b/c I want to see how the GB stock build will be) and I have the old Android Market (from 6+ months ago) app and it's not updating to the current version. I have rebooted the phone, FC'd the Market, everything short of doing an annoying factory reset and starting over after one day of use - still no new Market.
Anyone else having this problem? Any fixes?
Thanks in advance!
Give it a day at least mine usually automatically updates itself after a while once I'm logged in my account and connected to servers
Sent from my LG-P999 using XDA App
Are you synced? Try logging to to gtalk.
Related
I was just on the market and I saw that there is an update for the t Mobile My Account app. Has anybody installed this yet? I'm wondering if this fixes the WiFi issue I had with the 5.6 update freezing DNS which is the reason why I rooted my G2X. I'm also hesitant because I currently have the my account frozen.
Sent from my LG G2X (rooted) using XDA Premium.
I typically try to avoid T-Mobile software like the plague... no convenience is worth having their programming gum up my phone.
I'll remain hopeful though that T-mobile will start getting their act together starting with updating their apps and fixing them proper. Despite my angst against the topic I'm still curious regardless.
My wife's s4g got it last night but not on my g2x
I downloaded it last night. It is still a buggy mess. It takes forever to sync with Tmo and half the features do not work. Billing and Plan still do not sync. It just gives a message to call to get the info after about five minutes of doing nothing.
Activity/data used does work which is nice for those stuck on the 2g plan.
Still a horrible app...Delete.
jcbofkc said:
I downloaded it last night. It is still a buggy mess. It takes forever to sync with Tmo and half the features do not work. Billing and Plan still do not sync. It just gives a message to call to get the info after about five minutes of doing nothing.
Activity/data used does work which is nice for those stuck on the 2g plan.
Click to expand...
Click to collapse
It is even buggier than before, I might try restoring the old version
Well I'm glad I didn't update
Based upon the results so far I'm glad I left that update alone.
Uninstalled. That thing sucks. How hard is it for a company the size of TMo to build a half decent app?
I had to uninstall updates then reinstall and reboot. After all that mine syncs all fields just fine and I find it to be a great resource to monitor my usage since no matter what 3g watchdog says, T-Mobile will be throtling me for what they see pass-through for data. Its also super easy to pay my bill with.
Sent from my T-Mobile G2x using XDA App
UCFJake said:
I had to uninstall updates then reinstall and reboot. After all that mine syncs all fields just fine...
Click to expand...
Click to collapse
I didn't even have to do that; I just updated it in the market and it all just works fine for me. (I don't use it very often and didn't immediately open it after the update, so it's probable that I did have a reboot in there somewhere between the update and the first time I used it.)
dunno why u guys are having so much trouble with it. works fine for me even before the update
Hello everyone,
I've had the gingerbread update for about two days now and the android market doesn't seem to be acting right. I happen to be stuck with the old market even though I had the newly updated market before I went all gingerbread man. Then to make matters worse when I try scrolling down to look through more apps it doesn't load anymore of them, it just shows like 10 max. Any possible solutions to this?
Just install the new market. There is a thread somewhere in themes and apps with it I believe.
Sent from my Inspire 4G using XDA Premium App
or wipe your device and re-sync it. i lost my apps in the marketplace over a rom flash. i wiped the dev via the bootloader and let it sync again... been fine ever since.
I have the old market too for the time being, I'll enjoy it while I can. I hate the new market and think it's bloated crap
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
neonflash said:
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
Click to expand...
Click to collapse
The most likely issue is the fact that it is running a dual boot and your SD card is messing up. I never advise dual booting as things like this can happen. I would reflash a stock rom. Then go from there. Also might find more help in the captivate section.
Thread closed
Sent from my SGH-I777 using Tapatalk 2
Running totally stock on 5.1.1 (N920PVPU2A0I6). Starting about an hour ago I'm getting a pop-up saying "Bootstrap Failed...".
Phone is unresponsive and reboots by itself.
Thoughts?
late,
Coz
*EDIT: Factory reset didn't solve it.....correction, 3rd attempt at factory reset seems to have solved it. But I would love to know what initially caused the situation.
Same
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
Same
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
The only thing that updated/changed this morning was an update (I believe) for Sprint Zone.
late,
Coz
Well that didn't work....after about an hour of it running without issue, I'm getting the Bootstrap Failed... message again and it's restarting.
late,
Coz
Update....phone has been stable (no re-boots, lock-ups, etc.) for the past few days. I occasionally get the pop-up message stating, "bootstrap failed..." but it doesn't seem to impact the performance of the phone from what I can tell.
late,
Coz
Mine keeps doing it oh well
Sent from my SM-N920P using XDA Premium HD app
My phone just started doing this today. Also a Sprint Note 5. No software updates installed recently... most recent was the Sprint and Samsung updates for Samsung Pay, which I did set up-- but I did that day 1. Right before the problem started happening, the phone rebooted itself, and it hasn't been well since. I checked aLogcat, but nothing gets logged there. After a few of the "Bootstrap failed..." toasts, the phone just becomes unresponsive and I have to hard shutdown. The only thing that I can think of that I've done differently today was plug my phone into my laptop to charge it earlier. I don't think I'd ever plugged it into my laptop before.
Hopefully somebody can pin down the cause of the problem here. I'm surprised that aLogcat doesn't show anything, which makes me wonder if it's some Knox issue...
U have to use root explorer and go to carier/itson delete that folder it will make your phone faster but u need to power it off for like 20 mins afrer u delete it
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
U have to use root explorer and go to carier/itson delete that folder it will make your phone faster but u need to power it off for like 20 mins afrer u delete it
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
I'm curious as to why you suggest deleting that folder? What exactly will that fix? Details please before you suggest to a member to just delete something.
late,
Coz
The reboots i saw it mentioned.
Sent from my SM-N920P using XDA Premium HD app
Same problem, I have stock Sprint Note 5 with Samsung Pay updated and activated. Worked fine for a few days then all of the sudden I started getting "Bootstrap Failed" and my phone is unresponsive and/or data connection stops functioning forcing me to restart.
Is Sprint/Samsung aware of this issue and working on a fix? Very annoying. I've uninstalled all updates to Sprint Zone, force stopped and cleared data for Sprint Zone which appeared to help for a couple days, but now it's back again.
Has anyone had any luck with hard / factory reset? I don't want to go through the hassle of backing everything up, wiping it clean and reinstalling everything if at the end of the day it doesn't make a difference.
After a few more lock ups and reboots yesterday, my phone started behaving normally again, but just now I saw another "Bootstrap failed..." toast, so clearly the problem has not gone away. It hasn't locked up again on me yet, so maybe I'll be okay for a while. The only references I've seen to this error have all pointed to the Sprint Note 5, and most have mentioned Samsung Pay, so I suspect it's an issue there. Whether or not Samsung/Sprint are aware of it, I don't know.
I've also read it may or may not have something to do with Sprint Zone. I would agree it's purely due to the recent Samsung Pay update as I've had the Note since launch day and only noticed this after activating and updating Samsung Pay late last week. Before that I used the phone for nearly a month with no issues whatsoever.
While my phone hasn't locked up or rebooted by itself, I still get the "bootstrap failed..." occasionally.
I too think it was associated with the Sprint Zone and/or Samsung Pay update.
late,
Coz
I have only seen it once. Im fully stock to latest update. It happened to me after i noticed i had no data connection showed full lte but i had nothing opened up sprint zone and tried to refresh showed error. Then bootsrtap failed, have not seen it since
Sent from my SM-N920P
Bootstrap failed
It started happening to me after my fingerprint recognition failed, and I could not remember my backup password.
Just started happening to me a few days ago. completely stock sprint phone with the latest update (samsung pay). I noticed that right after the message PRL update began. After that and updating the profile, i havent seen the message.
Any updates on this? I went into Best Buy this weekend and had Samsung Experience store re-flash the OS to the phone, uninstalled Sprint Zone, uninstalled Samsung Pay updates, and force stopped Samsung Pay Framework. It worked fine for a few days but it started showing "Bootstrap failed" again. While it doesn't freeze up like it did the first time I received that message, in general the connectivity seems spotty (I'll show I'm connected to Wifi but nothing shows up on web browser or apps).
The problem is when Samsung Pay installed, it also installed an update to Android, and the Samsung Experience store in Best Buy can only flash the latest version of the OS. They can't revert back to the stock version of Android that came with the phone.
That's the biggest problem. Samsung and Google should make it so that they can revert back to a prior version of Android if the latest version has major bugs in it (which has been increasingly the case since Lollipop began rolling out). I had ZERO problems with the stock software/firmware that came with the device out of the box. Lesson learned I guess, don't accept an update if the version you have works well, until at least a couple months of the new update being out in the wild first....
Haven't seen this notice in a few days. It stopped after manual prl and profile update.
On a side note, I disabled the Samsung pay via package disable pro
Anyone figure this out?