Related
I got it from AMAZON last week. First couple days it was great. I won't say it was better than my gf's iphone 4 but certainly it was close, considering I got it free.
Then yesterday the cell phone signaled a system update, downloaded, started to update, indicating "update fail, the system will reboot automatically". It never did....
I tried everything I can find, could not even get to the download mode. Actually can't get anything from the screen. I found in ATT only communities that apparently it is a common problem...
Luckily amazon is going to send me a new one... although I lost all my stuff...
Anyway, just give your guys a notice that don't do "system update" on your phone. It will brick it.. Is there anyway to update it though? I am not sure...
zhaoyuji12 said:
I got it from AMAZON last week. First couple days it was great. I won't say it was better than my gf's iphone 4 but certainly it was close, considering I got it free.
Then yesterday the cell phone signaled a system update, downloaded, started to update, indicating "update fail, the system will reboot automatically". It never did....
I tried everything I can find, could not even get to the download mode. Actually can't get anything from the screen. I found in ATT only communities that apparently it is a common problem...
Luckily amazon is going to send me a new one... although I lost all my stuff...
Anyway, just give your guys a notice that don't do "system update" on your phone. It will brick it.. Is there anyway to update it though? I am not sure...
Click to expand...
Click to collapse
Since this is your first post, let me direct you here and point out Forum Rule 1:
http://forum.xda-developers.com/announcement.php?f=263#td_post_81
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
http://www.wtfokc.com/sef****/badkitty.gif
welcome to XDA
Closing this thread.
Here's a new one, at least for me...when I hit my system update check button in about phone, my Bionic is spitting out
"check for update is not available
at this time.
Try again later,"
Has anyone else ever seen this message? It looks like its happening on 4G or wifi, haven't forced 3g and tried yet.
Usually I expect the "Your phone is up to date" message, but this one's new to me.
I'm bone stock, btw...no rooting yet.
I got that a few times yesterday and then tried again 10min later and it ran the check successfully but didn't find an update. When I ran the check for updates this morning it found the update and downloaded/installed successfully.
Well, that's encouraging I suppose...every time I think I really like this phone, something like this pops up...ugh, I want bionic speed and HP, but with my OG droid and droid X's "it just works" reliability.
I think the only reason you're seeing this error is because the servers are under a very heavy load pushing out the updates. I never saw this error before yesterday. But I'm with you on the frustration factor. I'm on my 4th Bionic now, if I continue to get the black screen of death, random reboots, or data connection issues, I'm going to do whatever I can to get a different phone. I've never had to return a phone to Vz before this model, nor I have ever spent so much on a phone. I certainly don't feel like I'm getting what I paid for. How this phone made it thru user testing with these issues blows my mind.
I had been getting that message ever since I replaced my SIM a couple months ago. I figured it wouldnt interfere with me getting any OTA's, but last night I decided to do a factory reset to see if that cleared it up. Low and behold i hit system updates and it said my system was up to date. An hour or so later I did it again and I got the update!
Good to know. I read a thread somewhere, I think it pertained to battery issues, and someone suggested that when you first take the phone out of the box the first thing you should do is a factory reset b/c it helps with overall performance. I don't know if there's any truth to that but that's what I've done on all of my replacement Bionics and I do perceive there to be some improvement. I don't know if it was necessary but I ran the reset after receiving the OTA today too just to rule that out if I have issues going forward - that's the first thing tech support makes you do when you have problems from my experience anyway.
I've been getting that message a lot too when checking for the update. I got the update today and it installed fine. Still have the data drops though. VERY frustrating.
One think I HAVE noticed with this update is that the battery stats are completely reversed. It used to be the display was down in the 3-5% region, as well as the Android OS. Now, those 2 are at the top, and my phone has just been laying on my desk most of the day.
I am not rooted. I've been getting that message since I got the phone in October. It only happens when I am on 3G. I haven't checked it on 4G (don't live near one) and it says "...up to date" when I am on WiFi.
Sent from my DROID BIONIC using xda premium
I am getting frustrated... I have been getting the same error for three days now. I am rooted, but am on 5.5.886 and everything still the same. My partner is still original stock, and he's getting the same errors as well. Perhaps this is a regional thing? Anyone in the DC area get the update rolled out to them?
Additionally, can I just flash the update file that is posted here on the forums to upgrade manually? Or should I just wait?
Works!
I was getting the same "check for updates not available at this time" message, however I rebooted (used Quickboot, battery pull is not necessary). After the reboot went back to "Check for upgrade" and it worked; BUT just like the previous upgrade the process checks your file system and if you removed/altered any bloatware then it will fail and reboot. After the first time, I decided instead to create a folder "bloatware" in the system direction and move all bloatware apps to that folder. So this time around all I had to do was move all the bloatware back to the "app" folder in one shot. Very easy and straight forward (I also wrote down the bloatware apk filenames so I didn't forget that I moved over last time). Tried the update again, installed just fine, and phone is up and running.
AND....root is INTACT!
Btw...I had no idea there was a new update available until my friend who just got a new Bionic said he's having problems rooting on software v5.9.902
I am wondering how stop an update on a Droid Bionic?
I understand you need to "move the update from /cache to your SD card" once downloaded.
However, I do not know where "/cache" is located, how it is accessed, or how the moving process is done.
I connected my phone to a PC via USB and could not find "/cache" stored on the phone. The only thing close was a cache folder within "com.google.android.apps.maps", which doesn't seem like what I'm supposed to be looking for. I've also tried looking in Menu>Settings>Storage but do not see any 'cache' info.
I've been searching the forums but have had no luck; plenty of references to a 'cache' from
people who clearly know what they are talking about, but I can not find any explanations or instructions.
Any help is appreciated. This is my first Android device btw! (though I've been reading this forum for a week or two now)
Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
root .902
http://www.droidforums.net/forum/droid-bionic-hacks/198045-902-root-method.html
advanced root and play with leaks and return (well written, read 1st post several times,) also has links to current drivers
SamuriHL spends his life supporting that thread and spends too much time helping others
http://www.droidforums.net/forum/droid-bionic-hacks/214902-downgrade-902-no-app-data-loss.html
I'm not sure if I helped or confused, mainly just want you to be aware
greeneink said:
Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
Click to expand...
Click to collapse
thanks; that's really what I needed, a point in the right direction. I confess it's a bit new to me. I just got this phone, programmed it using steps found here (great forum!), and activated it on pageplus, but this was the first time I just got 'stuck' on something.
I read that 3G worked much better with 902 than with 905. this is why I was thinking of sticking with 902, at least until a legit/finalized version of ICS gets released (which allegedly, is very soon...maybe). Since I don't know much about the OS yet I figured I could survive the wait without 'knowing what I'm missing' so to speak.
whoa, just googled and saw that a new leak is out. I picked an odd time to be a newb working on a Bionic.
Thanks again!
If you do take the plunge into a leak, you should probably stick to one where FXZ to 902 isn't blocked so you can return to stock if needed. Everything 235 and after is poison, so to speak, and you won't be able to go back, which (thanks Moto) makes it really difficult to go forward (thanks Moto). I'm on 232 and I'm happy as a clam. It's stable and doesn't have many issues. Now when the official update comes out, they should release an FXZ and we'll be safe again and can all take the dive into ICS.
so, I realized you could postpone the update by just not accepting it when the prompt comes up.
so, I use my Bionic for a while and am quite happy. Then today, I noticed I no longer had 3G service. I tried restarting it, removing the battery,
toggling some of the data changes, no luck. I figured since ICS is (allegedly) right around the corner, there was really no reason not to go ahead and update.
I ran the update. I now have no phone service, no texting, and no 3G/1x.
My question is: how far in the process do I need to go back to get things running again? Right now what I have is a blinking white triangle in the notifications bar. My phone is stock in every way.
Edit: in "about phone/status" I have no phone number (it's blank). no MIN, no network. My PRL version is 'unknown'. so, basically I think I need to just start over, using the info I used successfully before (adam3rd is my hero), beginning with flashing a pageplus PRL. but I shouldn't need to reactivate it on pageplus, or need a new sim card, right? I feel like whatever happened wouldn't have effected my status with PP or the sim card, but I can't find a clear answer....any help appreciated
The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area
greeneink said:
The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area
Click to expand...
Click to collapse
thanks for the response. I actually had 4 bars of signal strength along with the white triangle. I'd assumed this meant I could 'detect' the verizon/PP network but wouldn't be able to get out of 'roaming' status until it was activated for the network.
I actually contacted PP via chat to reactivate it. they did it, but the problem wasn't resolved so I tried a factory reset. boom, activation screen came up! now I have fone and text again.
my real problem now is getting data to work consistently. gonna wait until the legit ICS comes out before tackling that one again.
You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience
greeneink said:
You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience
Click to expand...
Click to collapse
yes, I'm very excited. a little paranoid about updating since I'm on PagePlus and haven't seen anyone use Pageplus and .246 yet. but I may just try using the info on howardforums; I know it 'should' work, but that's just not the same as confirmation.
on a side note; I believe I may have discovered what my data problem was; I think I'd just disabled the 'connect with data over mobile network' option and forgotten I'd done so a month later. pretty funny. but it's been a good learning experience, heh
Hi everybody, I'm new to LG, this is my first LG phone since my original LG Vu many many years ago, and i have a couple questions. I've searched everywhere here on XDA and a couple other forum sites, as well as general google searches. First off my Flex is on 4.2.2 and it doesn't seem I have any way to update to 4.4.2. Whenever I try the update from my phone it says "your phone is not registered" and when I try with the LG computer software it just says my device is up to date. I've seen the not registered error mentioned a few times before and I tried the suggestions given, like getting a new sim card and doing a factory reset, but no luck. I've seen a few people mention that they flashed the update manually with something called LG Flash Tool, but I cant find any info on that whatsoever. My model is the AT&T D950 by the way. Secondly I am having absolutly horrible lag with this phone, specifically list scrolling, mostly in apps such as Google+, YouTube, and Facebook, all the reviews i read before getting the Flex said it was super smooth, thays why I got it, so is there something I should so, or is lag like this normal? Because I can't scroll through YouTube or Google+ without it hanging every couple seconds. If anybody that has more experience then me with this phone or LG in general could help me out with these or just point me in the right direction, that would be greatly appreciatex.
zacharyt86 said:
Hi everybody, I'm new to LG, this is my first LG phone since my original LG Vu many many years ago, and i have a couple questions. I've searched everywhere here on XDA and a couple other forum sites, as well as general google searches. First off my Flex is on 4.2.2 and it doesn't seem I have any way to update to 4.4.2. Whenever I try the update from my phone it says "your phone is not registered" and when I try with the LG computer software it just says my device is up to date. I've seen the not registered error mentioned a few times before and I tried the suggestions given, like getting a new sim card and doing a factory reset, but no luck. I've seen a few people mention that they flashed the update manually with something called LG Flash Tool, but I cant find any info on that whatsoever. My model is the AT&T D950 by the way. Secondly I am having absolutly horrible lag with this phone, specifically list scrolling, mostly in apps such as Google+, YouTube, and Facebook, all the reviews i read before getting the Flex said it was super smooth, thays why I got it, so is there something I should so, or is lag like this normal? Because I can't scroll through YouTube or Google+ without it hanging every couple seconds. If anybody that has more experience then me with this phone or LG in general could help me out with these or just point me in the right direction, that would be greatly appreciatex.
Click to expand...
Click to collapse
If you are on AT&T, take the phone to the store and have them update it for you. If you are on another carrier you will have to manually flash the update. As for the lag, I have also just got the Flex and I have not had any lag, but I have always done a Factory data reset before I do anything else.
TheMighyLoki said:
If you are on AT&T, take the phone to the store and have them update it for you. If you are on another carrier you will have to manually flash the update. As for the lag, I have also just got the Flex and I have not had any lag, but I have always done a Factory data reset before I do anything else.
Click to expand...
Click to collapse
Yeah I'm on AT&T. Thanks for the tips, I really appreciate it. Unfortunately nothing seems to work. I've tried downloading the LG PC software from their website but it just tells me I'm up to date, I can't find any info on how to use the LG flash tool thing, and I just went into 3 different AT&T stores, one of which was a device support center, and they all said they have not way to flash the LG G Flex because LG stopped supporting the tool they had to flash it with so it no longer works. So it looks like I'm stuck on 4.2.2. It's a shame really because I really got this phone to test out LG before the G3 comes out to see how I would like it since I'm up for an upgrade, and I absolutely LOVE it, but I'm not dropping money + a contract on a phone that might have issue upgrading the software, I mean we already wait long enough for android updates on non-nexus phones, but then even when it's available you can't update it because there is some sort of issue between AT&T and LG servers. And the worst part is it's not just me or this model phone. I have seen tons of people having the same issue with G2's and G Pro 2's but nobody seems to be able to figure it out. It really suck. But thanks for all the tips and help, like I said I really appreciate it!
Just want to give an update for anyone else that has this issue and might come across this thread. After going to 2 more stores, getting 2 more new SIMs, and 2 more factory updates, then spending about an hour on the phone with tech support with them trying to "push" the update to me, then another 2 hours on chat support with them trying to "push" it to me, I am no closer to any kind of solution.
Just another update, AT&T filed a case and I can now check for software update through settings, and it tells me an update to 4.4.2 is available, but once it downloads the update fails, it tell me my device is suspected of rooting and software update is not available for my device. My device is not, and has never been rooted. So I don't know where to go from here. This is the most frustrating thing I have ever encountered in my 4+ years with android lol. My next phone will definitely not be an LG phone, which is a shame because I just got this one to test out LG while waiting for the G3 to make it to AT&T.
did you buy this new?
isnt there a warranty from ATT?
zacharyt86 said:
but once it downloads the update fails, it tell me my device is suspected of rooting
Click to expand...
Click to collapse
Can you post a screenshot of the message you're getting that says your device is suspected of rooting?
Yes I bought it new from an AT&T COR store. Yeah it has warranty, I actually just went to the support center and exchanged it after explaing that it has never been rooted or else I would post a screenshot, I didnt even think about doing that, I remeber the error exactly though, I must have tried it a dozen times. When I went to software update it said a new update is available and I clicked yes to download, after it downloaded it rebooted into that LG screen with the cartoony hills and stuff and it said updating 0% for about 2 mins, the in big letters it said ERR:0x0011341, and it rebooted back into the ROM and everthing loaded up, after about a minuter I got a popup that said Error: Your device is suspect in rooting, your device is not available for software update, then any time I tried to run software update that popup would come back up unless I did a factory reset, then it would start the whole thing over with the same results. Like I said, I just got a replacement and am downloading the update now, I'll post back and let you know what happens.
Its not that unusual for a phone to get hosed when trying to download/install an OTA update.
Is is unusual for a message like you saw, about being a "suspect" for rooting; I don't think I have ever heard of that before..
All that matters is you got a new phone, so thats a good thing
Yeah i thought it was weird too, the weirdest pat was i did the return to stock from the other thread here just to see if that would fix the issue and it still said the same thing, it even did it after factory resets, like something had been tripped and couldnt be reset. Im no stranger to rooting, I've been doing it for years, i just never did it with phone cuz there isn't a whole lot you can do with it. But the new one just updated to 4.4.2 no problem so the issue is fixed. It was all just really strange, i found a thread here from another person getting the same error on a G2 http://forums.androidcentral.com/lg...tware-update-not-available-rooted-device.html
zacharyt86 said:
Yes I bought it new from an AT&T COR store. Yeah it has warranty, I actually just went to the support center and exchanged it after explaing that it has never been rooted or else I would post a screenshot, I didnt even think about doing that, I remeber the error exactly though, I must have tried it a dozen times. When I went to software update it said a new update is available and I clicked yes to download, after it downloaded it rebooted into that LG screen with the cartoony hills and stuff and it said updating 0% for about 2 mins, the in big letters it said ERR:0x0011341, and it rebooted back into the ROM and everthing loaded up, after about a minuter I got a popup that said Error: Your device is suspect in rooting, your device is not available for software update, then any time I tried to run software update that popup would come back up unless I did a factory reset, then it would start the whole thing over with the same results. Like I said, I just got a replacement and am downloading the update now, I'll post back and let you know what happens.
Click to expand...
Click to collapse
I'm having this same issue, but I did root my device. I completely unrooted it, and tried again with no luck. I thought it was me. Looking forward to hearing if you have success with the replacement. If so, I'm definitely taking this guy in. ?
Sent from my LG-D950 using xda premium
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.