WP8.1 Weird Store Bug: App Stuck at "Installing", blocking other app Updates.
Ok, so I've a pretty bad bug that stopping me from updating my apps.
I decided to try Unified remote (though I think this could have happened to any app) and when it got to installing, progress bar at about 60%, it stopped.
I waited a while, nothing moved, I went to look at it in the app list and it was done. I opened it, used it for a bit, it was fine. Back to the store, and it still says "Installing".
When I long press the install, nothing happens. The element moves, but no options drop down to cancel or pause.
So I go ahead and restart my device, thinking this would clear it up. I forget about it for about a day, go back to check and it's still there!
Windows phone does VERY LITTLE in parallel, so apps only download one at a time, all waiting on the first to finish installing... so you can see where this is going, the app is still marked as "Installing" and all other apps are now "Pending".
I went ahead and deleted the app, and that didn't help. Restarted once more for good measure to no avail.
Long press again still gives me no options.
Anyone ever had a situation like this? Know of a way to unstick this app that does not include a device reset?
Appreciate any help.
Hi, after doing my fire 7, my dad gave me his memopad 7hd k00b ( I believe) to try and "fix" Essentially I think it got rooted, and flashed, but something went wrong. On the start up/set up for android of some description, everything seems to pop up as stopped working, click ok. Everything, I've seen superuser, chrome etc. By clicking OK on all these boxes, You can get to screen 5 of 8, where it asks to set up google account, then you get process.com.google.process.gapps has stopped. To then try and fill in screen 5, you have to click ok to that message, however it then resets the set up and you go back to screen one (select Language etc). I can't get past that.
We're talking last year, early quarter perhaps that this was done, so it's just sat and stewed doing nowt since then.
Is there anyway I can "fix" this?
I wanted to reply to myself to say eventually got it sorted. I used something called SP Flash Tool V3 which, following a guide, allowed me to reflash it, unlock it perhaps, not quite sure, but needless to say allowed me to get access to boot loaders(?) and then flash on a new rom. So I have it back working again. Most replying just in case someone else is searching globally and it comes up.
Not sure why, but a friend has a S8+ tmobile and the install from unknown sources ALWAYS turns itself back to OFF....? Is there some trick to making it stay enabled?
I'm pretty sure it's happening to everyone. Feel like it's their way of saying repeatedly that they would rather you not sideload apps that you probably got for free instead of paying haha. I've done research on this as well as its more of an annoyance. Most likely will have to wait for root
Yep happens on mine also
Yup, here too. Waiting for root sucks! Hopefully something will be verified soon. You guys should really google "SM-N950U root and you'll find a slew of root methods, I'm just too scared to try them. I wish they would just say error and nothing happens rather than have the potential to brick your phone. Oh well, waiting it is.
Nathan.7118391 said:
Yup, here too. Waiting for root sucks! Hopefully something will be verified soon. You guys should really google "SM-N950U root and you'll find a slew of root methods, I'm just too scared to try them. I wish they would just say error and nothing happens rather than have the potential to brick your phone. Oh well, waiting it is.
Click to expand...
Click to collapse
Trust me, as a dev myself, you dont want to listen to those. They have been tried already. And if they worked, it would be posted all over here as all the s8's on each carrier are the same phone. We are all working diligently to figure it out.
Except me right now. I'm at the doctor refilling my adderall so I can binge work on it all weekend hah
Acoustichayes said:
Trust me, as a dev myself, you dont want to listen to those. They have been tried already. And if they worked, it would be posted all over here as all the s8's on each carrier are the same phone. We are all working diligently to figure it out.
Except me right now. I'm at the doctor refilling my adderall so I can binge work on it all weekend hah
Click to expand...
Click to collapse
Haha yup I hear you. Thanks for your help on this. Keep healthy bro!
Well I'm sorry the unknown sources not sticking is a real thing... but I'm glad its not just her phone. I was convinced something was wrong and almost reflashed the firmware just because.... but it's obviously that way for whatever the reason. You just have to turn it on before each install I suppose. No big deal.
As for root, the eng boot was leaked or developed or whatever you want to call it... bottom line its in the wild now, so I think sooner rather than later there will be at least a eng boot type of root. Nothing compares to a real unlocked bootloader. *IF* I get a Samsung again, it will be the Exynos ###F model with a unlocked bootloader... But I'm a flashaholic....... otherwise ROOTING is becoming like jailbreaking is for the iPhone (non-existent).... at least for us USA owners anyway
I had this issue at first. This is my first Samsung phone since the Note 3. I thought it was something to do with KNOX. But after a week, I reset my phone, set it up as usual. And now the unknown stays. I can't recall what I did different, but I know wiping it did something.
Araltd said:
Not sure why, but a friend has a S8+ tmobile and the install from unknown sources ALWAYS turns itself back to OFF....? Is there some trick to making it stay enabled?
Click to expand...
Click to collapse
It's a bug. Should be corrected with a future update.
From what I've done, I believe it's actually Google turning it back on with the feature in settings, verify apps. Just turn it off and it shouldn't turn off the untrusted sources anymore. Since turning it off, I haven't had issues
Acoustichayes said:
From what I've done, I believe it's actually Google turning it back on with the feature in settings, verify apps. Just turn it off and it shouldn't turn off the untrusted sources anymore. Since turning it off, I haven't had issues
Click to expand...
Click to collapse
I think that did the trick for me. I had thought I already turned that off but it came back. Once I disabled that though my unknown sources has stayed at least for a few hours now and through me installing some stuff.
EDIT: there it goes back off again! doesn't seem to be anything we can do
sm-N950 custom navigation bar icon colors
Acoustichayes said:
From what I've done, I believe it's actually Google turning it back on with the feature in settings, verify apps. Just turn it off and it shouldn't turn off the untrusted sources anymore. Since turning it off, I haven't had issues
Click to expand...
Click to collapse
How were you able to change the navigation bar icon colors from the default white to green on your sm-N950?
I have turned ON "UNKNOWN SOURCES" on my phone 2-3 days ago and it is still on.
Anyone still having this problem?
What about the built in security app lookout, I have that and the google play verify off and have never had the developer option turn its self off I think it may be that app blocking harmful apps that we want to sideload by keeping that turned off maybe lol:good::highfive::goodI have had mine on since about mid sept. when i got the phone)
A few days ago, I was trying to launch an app from my phone's home screen when it suddenly rebooted itself and downloaded/installed an OTA update, removing root in the process. So it looks like Google just force-restarted it and updated it without my consent!
Or, if not that, then I truly must have the worst luck imaginable - like astronomically, unbelievably bad; so bad it could be legendary - almost as if I were cursed by some mythical, malevolent creature with magical powers.
For what I'm about to assume might have happened to be what actually happened, the odds are probably astronomically against it occurring, or nearing the realm of quantum impossibility (or, at the very least, it would be extremely-improbable and highly-unlikely, statistically speaking).
There have been a handful of times (3-5, but I haven't kept count) in the few months I've had this phone that, after unlocking the screen, I see a window drawn over my phone's home screen: a notification dialog with info about downloading/installing a security update for the OS. At the bottom of the window I recall there being two buttons: one to confirm, reboot my phone, and download/install the update, and the other to postpone the update until some later time at night.
Since there was no button for the polite, socially-acceptable equivalent to responding, "NO, **** YOU! STOP ANNOYING ME WITH THIS PROMPT TO UPDATE! I NEVER WANT TO DOWNLOAD AND INSTALL AN UPDATE, OR SEE THIS POP UP EVER AGAIN!", I've just used the "back" button on my phone to dismiss this notification/prompt rather than accepting one of the two equally-unacceptable choices it offered me and being forced into downloading and updating my phone.
So, in theory, it's possible that, at the same exact moment as my phone's screen refreshed to draw this update notification/prompt again, I just happened to also click in exactly the wrong place - the place where that dreaded "reboot" button was drawn - thereby selecting the option to immediately reboot my phone, downloading and installing the update in the process. It would've had to have happened so quickly - literally, within the same 1/90th of a second - that the screen was drawn so that I didn't even see the notification appear before clicking the option to accept and reboot/install the update immediately.
1/90th of a second: that's just a hair over 11 milliseconds, or a hundredth of a second. And I just happened to click in exactly the wrong spot at exactly that moment?
Utterly, unimaginably, and even ridiculously bad luck if this is what actually happened. But aside from Google simply forcing a reboot/update remotely while I was using my phone, it's the only other thing I can think of that might've caused this.
Whoever programmed this functionality should at the very least be publicly shamed and insulted for it, but possibly also dragged out of their bed in the middle of the night into the street and beaten mercilessly. I don't know the law well enough to be aware of the name of the crime for such a thing (annoying millions of people with this almost-unavoidable and heinously-obnoxious nag to update their phone's OS, and causing maybe thousands of them to suffer some sort of financial loss, pain & suffering, or tragic inconvenience by accidentally accepting and applying the update - especially if they happened to be on a limited mobile data plan, or were roaming at the time). However, I'm fairly certain that most people who have experienced something like what I've been through and am forced to deal with now as a result of an OTA update being applied against their will would be fine with either or both of these things being administered as the just and appropriate form of punishment for such a crime.
So, all that being said, what are my odds that I'll be able to not only restore root to my phone without wiping it and losing all the sensitive data I had saved with root access but hadn't had the time to back up yet during one of the most difficult and tragic weeks of my life (I can't even begin to explain all of the other **** that has gone horribly wrong recently), but to also recover compensation for the cost of exceeding my data plan while visiting another country due to the update being downloaded at an EXTREMELY inopportune time? My guess: probably worse than the odds of accidentally clicking to accept and immediately download and apply an OS update within the same ≈11 milliseconds the nag for it was drawn on my phone's screen while also in the middle of giving a presentation in a super-important, multinational business meeting.
But hey, I figured I would share this post here anyway in the hopes of maybe learning that Google force-pushed an OTA update and pissed off millions of people who then filed a class action lawsuit because of it, and I just hadn't heard the news about it yet, but it was also recent enough that I could still get in on that action and recover at least some part of what I've lost in the past week.
And if not that, maybe I'll at least somehow get confirmation of having some of the worst luck imaginable, or validation that I'm not crazy, or just some sympathy and comfort from the community during a very dark time in my life when I sorely need it.
And I guess if there's even a modicum of hope I'll discover that I'm not completely alone in this world of **** that I now find myself in, and that there are others who have suffered a similar fate or misfortune as a result of either unbelievably bad luck with their phone, or Google forcibly cramming something very large and uncomfortable into an extremely sensitive area against their will - maybe even at one of the worst possible times of their life - then maybe there's even some hope left for my life; some point to even continuing it and trying to get out of the horribly-****ty, godforsaken nightmare I'm stuck in right now.
Or maybe I'll just learn that it is actually somehow possible to restore root to my phone without needing to wipe it first so I'm at least not quite as completely screwed as it looks like I am right now.
≈-∞
Google Pixel 5, OS 11
rooted with Magisk, no TWRP/recovery
recently forcibly OTA-updated to build RQ1A.201205.011
Disable updates permanently. I'm more concerned with the damage updates will do than malware at this point
leveleyed said:
A few days ago, I was trying to launch an app from my phone's home screen when it suddenly rebooted itself and downloaded/installed an OTA update, removing root in the process. So it looks like Google just force-restarted it and updated it without my consent!
Or, if not that, then I truly must have the worst luck imaginable - like astronomically, unbelievably bad; so bad it could be legendary - almost as if I were cursed by some mythical, malevolent creature with magical powers.
For what I'm about to assume might have happened to be what actually happened, the odds are probably astronomically against it occurring, or nearing the realm of quantum impossibility (or, at the very least, it would be extremely-improbable and highly-unlikely, statistically speaking).
There have been a handful of times (3-5, but I haven't kept count) in the few months I've had this phone that, after unlocking the screen, I see a window drawn over my phone's home screen: a notification dialog with info about downloading/installing a security update for the OS. At the bottom of the window I recall there being two buttons: one to confirm, reboot my phone, and download/install the update, and the other to postpone the update until some later time at night.
Since there was no button for the polite, socially-acceptable equivalent to responding, "NO, **** YOU! STOP ANNOYING ME WITH THIS PROMPT TO UPDATE! I NEVER WANT TO DOWNLOAD AND INSTALL AN UPDATE, OR SEE THIS POP UP EVER AGAIN!", I've just used the "back" button on my phone to dismiss this notification/prompt rather than accepting one of the two equally-unacceptable choices it offered me and being forced into downloading and updating my phone.
So, in theory, it's possible that, at the same exact moment as my phone's screen refreshed to draw this update notification/prompt again, I just happened to also click in exactly the wrong place - the place where that dreaded "reboot" button was drawn - thereby selecting the option to immediately reboot my phone, downloading and installing the update in the process. It would've had to have happened so quickly - literally, within the same 1/90th of a second - that the screen was drawn so that I didn't even see the notification appear before clicking the option to accept and reboot/install the update immediately.
1/90th of a second: that's just a hair over 11 milliseconds, or a hundredth of a second. And I just happened to click in exactly the wrong spot at exactly that moment?
Utterly, unimaginably, and even ridiculously bad luck if this is what actually happened. But aside from Google simply forcing a reboot/update remotely while I was using my phone, it's the only other thing I can think of that might've caused this.
Whoever programmed this functionality should at the very least be publicly shamed and insulted for it, but possibly also dragged out of their bed in the middle of the night into the street and beaten mercilessly. I don't know the law well enough to be aware of the name of the crime for such a thing (annoying millions of people with this almost-unavoidable and heinously-obnoxious nag to update their phone's OS, and causing maybe thousands of them to suffer some sort of financial loss, pain & suffering, or tragic inconvenience by accidentally accepting and applying the update - especially if they happened to be on a limited mobile data plan, or were roaming at the time). However, I'm fairly certain that most people who have experienced something like what I've been through and am forced to deal with now as a result of an OTA update being applied against their will would be fine with either or both of these things being administered as the just and appropriate form of punishment for such a crime.
So, all that being said, what are my odds that I'll be able to not only restore root to my phone without wiping it and losing all the sensitive data I had saved with root access but hadn't had the time to back up yet during one of the most difficult and tragic weeks of my life (I can't even begin to explain all of the other **** that has gone horribly wrong recently), but to also recover compensation for the cost of exceeding my data plan while visiting another country due to the update being downloaded at an EXTREMELY inopportune time? My guess: probably worse than the odds of accidentally clicking to accept and immediately download and apply an OS update within the same ≈11 milliseconds the nag for it was drawn on my phone's screen while also in the middle of giving a presentation in a super-important, multinational business meeting.
But hey, I figured I would share this post here anyway in the hopes of maybe learning that Google force-pushed an OTA update and pissed off millions of people who then filed a class action lawsuit because of it, and I just hadn't heard the news about it yet, but it was also recent enough that I could still get in on that action and recover at least some part of what I've lost in the past week.
And if not that, maybe I'll at least somehow get confirmation of having some of the worst luck imaginable, or validation that I'm not crazy, or just some sympathy and comfort from the community during a very dark time in my life when I sorely need it.
And I guess if there's even a modicum of hope I'll discover that I'm not completely alone in this world of **** that I now find myself in, and that there are others who have suffered a similar fate or misfortune as a result of either unbelievably bad luck with their phone, or Google forcibly cramming something very large and uncomfortable into an extremely sensitive area against their will - maybe even at one of the worst possible times of their life - then maybe there's even some hope left for my life; some point to even continuing it and trying to get out of the horribly-****ty, godforsaken nightmare I'm stuck in right now.
Or maybe I'll just learn that it is actually somehow possible to restore root to my phone without needing to wipe it first so I'm at least not quite as completely screwed as it looks like I am right now.
≈-∞
Google Pixel 5, OS 11
rooted with Magisk, no TWRP/recovery
recently forcibly OTA-updated to build RQ1A.201205.011
Click to expand...
Click to collapse
yes, automatic system updates are turned off. it's the first thing i do when i set up a new phone. so like i said, either Google still forced an update on my phone - despite having the automatic update setting turned off - or i have unbelievably impeccable timing on top of horribly bad luck.
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
leveleyed said:
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
Click to expand...
Click to collapse
This is a simple solution and has been discussed before.
Get the boot.img for your current build
Copy it to the phone and patch it with Magisk Manager
Fastboot flash the resulting patched image
Accidentally OTA updated my pixel, all fine but root gone
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted. Of course my root is gone now, but i want to root it again. Bootloader is...
forum.xda-developers.com
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
l7777 said:
This is a simple solution and has been discussed before.
Get the boot.img for your current build
Copy it to the phone and patch it with Magisk Manager
Fastboot flash the resulting patched image
Accidentally OTA updated my pixel, all fine but root gone
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted. Of course my root is gone now, but i want to root it again. Bootloader is...
forum.xda-developers.com
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
leveleyed said:
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
Click to expand...
Click to collapse
Try downloading magisk directly and installing. Or are if it already downloaded it and install that one.
leveleyed said:
yes, automatic system updates are turned off. it's the first thing i do when i set up a new phone. so like i said, either Google still forced an update on my phone - despite having the automatic update settingl turned off - or i have unbelievably impeccable timing on top of horribly bad luck.
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
Click to expand...
Click to collapse
I'm sorry this happened to you.
But I think you more than likely thought it was off, I don't see why Google would "force" updates for only you.
leveleyed said:
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
Click to expand...
Click to collapse
Try downloading Magisk v22.
There is no longer Magisk Manager.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
l7777 said:
Try downloading magisk directly and installing. Or are if it already downloaded it and install that one.
Click to expand...
Click to collapse
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
leveleyed said:
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
Click to expand...
Click to collapse
Yes you should be able to uninstall it manually. Won't hurt anything.
leveleyed said:
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
Click to expand...
Click to collapse
No don't use canary, use v22.
But why can't you inside it? It's in Magisk settling. If you must uninstall it, you can try that also then install v22
andybones said:
I'm sorry this happened to you.
But I think you more than likely thought it was off, I don't see why Google would "force" updates for only you.
Try downloading Magisk v22.
There is no longer Magisk Manager.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Yeah, I know it was off because I am paranoid about automatic updates. I have them off in both Play Store and for system updates. I checked the setting after I rooted previously, and after it updated. So I guess it was actually just extremely bad luck/timing to click the location of the 'reboot and update now' button within the same frame the prompt appeared on my phone's home screen so that I never even saw it before it started rebooting and applied the update.
andybones said:
No don't use canary, use v22.
But why can't you inside it? It's in Magisk settling. If you must uninstall it, you can try that also then install v22
Click to expand...
Click to collapse
I couldn't unhide it because I was unable to launch Magisk at all. Every time I tried, I was just prompted to download it.
After uninstalling/reinstalling Magisk, downloading and extracting the boot.img for my current version of Android OS, patching in Magisk, and flashing the patched boot.img, I'm happy to report that I've successfully restored root without loss of my data partition!
Thank you so much to everyone here who helped me to get this resolved!
Now, hopefully I can find an app (or perhaps a Magisk module) that will prevent the system update notifications/prompts from even showing up on my phone, thereby eliminating the potential risk of needing to go through this again.