So a little bit of backstory to explain my question: I bought a brand new Nokia 8 this February and it was shipped with Android 8. I updated to Pie, but it pretty much bricked my device. I RMA'd it, and they exchanged it with another phone which I received a few days ago and again had Android 8 installed. However, since automatic updates was enabled, it has already started updating to Android 9. Currently, the update menu shows the following message:
Code:
Installation will automatically resume when the device is idle.
I have since disabled autoupdates by using the developer menu, but the message is still there. Now I'm kinda wary about updating to Android 9 again considering that it already bricked my device before, and besides I feel like Android 8 worked better for this phone, so I'd like to prevent this update.
So here's my question: Can I cancel this update by doing a factory reset through the Android menu (not recovery)? And if it is possible, is there any risk of bricking the device?
There's nothing I want to save on the phone since it's pretty much brand new, so resetting it don't bother me.
Thanks in advance!
KissShoto said:
So a little bit of backstory to explain my question: I bought a brand new Nokia 8 this February and it was shipped with Android 8. I updated to Pie, but it pretty much bricked my device. I RMA'd it, and they exchanged it with another phone which I received a few days ago and again had Android 8 installed. However, since automatic updates was enabled, it has already started updating to Android 9. Currently, the update menu shows the following message:
Code:
Installation will automatically resume when the device is idle.
I have since disabled autoupdates by using the developer menu, but the message is still there. Now I'm kinda wary about updating to Android 9 again considering that it already bricked my device before, and besides I feel like Android 8 worked better for this phone, so I'd like to prevent this update.
So here's my question: Can I cancel this update by doing a factory reset through the Android menu (not recovery)? And if it is possible, is there any risk of bricking the device?
There's nothing I want to save on the phone since it's pretty much brand new, so resetting it don't bother me.
Thanks in advance!
Click to expand...
Click to collapse
Factory resetting will temporarily remove the notification but it will come back after some time.
It may or may not be possible to block it for good, it depends on if anyone has found a working method for your specific model number. If it is possible on your device, it will probably require at least rooting the device.
Sent from my LGLS755 using Tapatalk
Try a factory reset + clear cache partition.
Droidriven said:
Factory resetting will temporarily remove the notification but it will come back after some time.
It may or may not be possible to block it for good, it depends on if anyone has found a working method for your specific model number. If it is possible on your device, it will probably require at least rooting the device.
Click to expand...
Click to collapse
Thanks for answering.
What if I factory reset the phone, then enable developers options and disable auto updates from there? Wouldn't that prevent the phone from downloading the update? And is there a any risk involved with factory resetting the phone while the install is pending? That's my biggest fear at the moment.
I don't want to root the device since it's still under warranty, I don't want to void it if there's a risk of the phone getting bricked again at some point in the future.
James_Watson said:
Try a factory reset + clear cache partition.
Click to expand...
Click to collapse
Thanks for answering.
I thought about doing that, but I'd rather avoid messing around with the cache. The warranty mentions that the only things covered by it are software wise are updates, so if I go around messing around with things I'm not theoretically supposed to I'm afraid it might void the warranty.
KissShoto said:
Thanks for answering.
What if I factory reset the phone, then enable developers options and disable auto updates from there? Wouldn't that prevent the phone from downloading the update? And is there a any risk involved with factory resetting the phone while the install is pending? That's my biggest fear at the moment.
I don't want to root the device since it's still under warranty, I don't want to void it if there's a risk of the phone getting bricked again at some point in the future.
Thanks for answering.
I thought about doing that, but I'd rather avoid messing around with the cache. The warranty mentions that the only things covered by it are software updates, so I go around messing around with things I'm not theoretically supposed to I'm afraid it might void the warranty.
Click to expand...
Click to collapse
If it is already downloaded and pending install, that means it has been downloaded and is being held in cache until you accept and start the process. You "might" be able to delete it from cache somehow and stop the process, possibly a factory reset from within system settings and then disabling update checks could work. It is worth trying.
Sent from my LGLS755 using Tapatalk
Droidriven said:
If it is already downloaded and pending install, that means it has been downloaded and is being held in cache until you accept and start the process. You "might" be able to delete it from cache somehow and stop the process, possibly a factory reset from within system settings and then disabling update checks could work. It is worth trying.
Sent from my LGLS755 using Tapatalk
Click to expand...
Click to collapse
The actual message that's displayed on the update screen is this:
Installation will automatically resume when the device is idle.
Click to expand...
Click to collapse
So the installation might already have started, I'm not sure. Would it still be safe to attempt a factory reset in these conditions? My biggest fear is that it might brick the device.
KissShoto said:
The actual message that's displayed on the update screen is this:
So the installation might already have started, I'm not sure. Would it still be safe to attempt a factory reset in these conditions? My biggest fear is that it might brick the device.
Click to expand...
Click to collapse
It may have started the process but it can't actually flash anything until the device is rebooted. I would still try the factory reset, if it doesn't work then you haven't lost anything as long as you backup your personal data and files before you reset. You can restore your data after the reset.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It may have started the process but it can't actually flash anything until the device is rebooted. I would still try the factory reset, if it doesn't work then you haven't lost anything as long as you backup your personal data and files before you reset. You can restore your data after the reset.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So it's 100% safe then? There's no risk of bricking the device by factory reseting it even though the update process has supposedly already started?
I'm sorry for being so paranoid, but I'm not very familiar with Android and considering the terms of the warranty, I reaaaaally don't want to screw anything up.
KissShoto said:
So it's 100% safe then? There's no risk of bricking the device by factory reseting it even though the update process has supposedly already started?
I'm sorry for being so paranoid, but I'm not very familiar with Android and considering the terms of the warranty, I reaaaaally don't want to screw anything up.
Click to expand...
Click to collapse
If the initialization of the update was only implemented at the system level, factory reset should wipe it. If it has initiated anything at the kernel/hardware level, resetting "might" cause issues.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If the initialization of the update was only implemented at the system level, factory reset should wipe it. If it has initiated anything at the kernel/hardware level, resetting "might" cause issues.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Is there any way to know if it has done anything of the kind by any chance? And what sort of of issues could potentially arise?
By the way thanks for taking the time to answer my questions, I greatly appreciate it.
KissShoto said:
Is there any way to know if it has done anything of the kind by any chance? And what sort of of issues could potentially arise?
By the way thanks for taking the time to answer my questions, I greatly appreciate it.
Click to expand...
Click to collapse
Another safe way to get rid of it is to just reflash the exact same firmware that you have(your current version, not the updated version). Flashing your current stock firmware via PC will reset everything exactly as it is supposed to be like before you triggered the update. Then you can try blocking the update before it happens this time.
Sent from my SM-S767VL using Tapatalk
KissShoto said:
So a little bit of backstory to explain my question: I bought a brand new Nokia 8 this February and it was shipped with Android 8. I updated to Pie, but it pretty much bricked my device. I RMA'd it, and they exchanged it with another phone which I received a few days ago and again had Android 8 installed. However, since automatic updates was enabled, it has already started updating to Android 9. Currently, the update menu shows the following message:
Code:
Installation will automatically resume when the device is idle.
I have since disabled autoupdates by using the developer menu, but the message is still there. Now I'm kinda wary about updating to Android 9 again considering that it already bricked my device before, and besides I feel like Android 8 worked better for this phone, so I'd like to prevent this update.
So here's my question: Can I cancel this update by doing a factory reset through the Android menu (not recovery)? And if it is possible, is there any risk of bricking the device?
There's nothing I want to save on the phone since it's pretty much brand new, so resetting it don't bother me.
Thanks in advance!
Click to expand...
Click to collapse
Hello! Yes, you can do a factory reset and get the Oreo back if you have updated to Pie.
https://www.techjunkie.com/perform-factory-reset-android-oreo/
esparkinfo said:
Hello! Yes, you can do a factory reset and get the Oreo back if you have updated to Pie.
https://www.techjunkie.com/perform-factory-reset-android-oreo/
Click to expand...
Click to collapse
Absolutely not, you can not got back to Oreo from Pie by performing a factory reset. That is not how factory reset works. Factory reset wipes the data partition and user settings, it does not do anything to the system partition at all. It especially does not "replace" the system with another system, it does not even "flash" anything, it only wipes.
Factory reset for android is nothing like the "restore to factory defaults" option that PC's have. They do not do the same thing. One "wipes" anything that was not factory installed to return to factory settings and the other formats and then "flashes" or "restores" a complete copy of the factory installed software to return to the original factory state. One wipes anything that doesn't belong and the other just replaces "everything", leaving nothing behind that was there before the replacement was applied.
I hope I made that make sense.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Absolutely not, you can not got back to Oreo from Pie by performing a factory reset. That is not how factory reset works. Factory reset wipes the data partition and user settings, it does not do anything to the system partition at all. It especially does not "replace" the system with another system, it does not even "flash" anything, it only wipes.
Factory reset for android is nothing like the "restore to factory defaults" option that PC's have. They do not do the same thing. One "wipes" anything that was not factory installed to return to factory settings and the other formats and then "flashes" or "restores" a complete copy of the factory installed software to return to the original factory state. One wipes anything that doesn't belong and the other just replaces "everything", leaving nothing behind that was there before the replacement was applied.
I hope I made that make sense.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for correcting my myth. I understood what exactly factory reset is and which can't be the solution of going back to Oreo from Pie. Then what would be the solution? Now I also have the curiosity to know more about preventing Pie updates.
Related
Recently I unlocked bootloader, installed twrp and succesfully rooted my device, but while I was tinkering with my device I accidentally wipe all data, partition, etc in TWRP now I guess I wiped out everything including OS !!!
How can I restore ? Do I need to flash new hammerhead image ?
Right now I'm following this tutorial
http://forum.xda-developers.com/showthread.php?t=2513701
It'll be great if anyone of you can point me right way.
You can just flash any custom rom using this
http://forum.xda-developers.com/showthread.php?t=2575150
Or
Follow the thread you posted to restore a factory image..
But restoring a factory image will unroot your device..
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Huh? You're doing an RMA why?
sent from my hammerhead
albertpaulp said:
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Click to expand...
Click to collapse
Why are you rma'ing it. Was wifi messed up before you erased everything?
jd1639 said:
Why are you rma'ing it. Was wifi messed up before you erased everything?
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
jd1639 said:
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Click to expand...
Click to collapse
Awesome advice. I made a nandroid of my N5 first thing after getting all my apps straight. Playing with flashing a rom in TWRP I did a manual "wipe data" which proceded to wipe out the entire SDCARD in the process including my nandroid. Sooooo.... Yes, make a nandroid but also back it up to your computer or dropbox right away.
albertpaulp said:
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
Click to expand...
Click to collapse
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
BirchBarlow said:
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
Click to expand...
Click to collapse
You know how to read right ? also I did reflashed to stock image and unrooted + locked bootloader but problem persists, what do you propose I do now ? I started loving my phone now I'm getting new one, it's hard for me too, it's like adopting a son.
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
simms22 said:
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
Click to expand...
Click to collapse
But this is showing up after rebooting, and I haven't used the camera for a few days. I also don't have any apps like skype that may be accesing it. Maybe I'm just being paranoid though.
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
rootSU said:
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
iJimaniac said:
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
Click to expand...
Click to collapse
Yeah you can use helium.
Sent from my Nexus 5 using Tapatalk
No issues here
iJimaniac said:
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
Click to expand...
Click to collapse
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
movielover76 said:
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
Click to expand...
Click to collapse
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Modified system
iJimaniac said:
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Click to expand...
Click to collapse
If your not stock your right, the OTA will likely fail. You can get away with being rooted, you'll just lose root.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
It's part of the price that comes with tinkering with your device.
movielover76 said:
If your not stock your right, the OTA will likely fail.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
Click to expand...
Click to collapse
Alright, good deal! Now I know for next time, thanks
Hi. I have a Oneplus one bought few years ago, never updated. Since few days I can't run "system settings" app : when I click on the wheel or on "system settings" nothing happens!!!!!!! So I can't pair a new bluetooth or wifi device .......:crying:
Any "easy" solution?
Thank you.
unlock your bootloader maybe, flash twrp and flash new rom, it might be rom issue, maybe
Sent from my A0001 using Tapatalk
Thank you, but is there not a easy way like downloading an system settings app?
Can't you just factory reset? It will reinstall system apps hence fix the issue.
Thank you.
When I read things about OPO factory reset, I can't understand what it erases exactly. I'd like to keep my apps and personnal datas.
Do you somethings about that?
ziaziung said:
Thank you.
When I read things about OPO factory reset, I can't understand what it erases exactly. I'd like to keep my apps and personnal datas.
Do you somethings about that?
Click to expand...
Click to collapse
Well, you could "dirty flash" from fastboot by flashing everything but userdata.img it will keep all your data and fresh install the OS. But only if you are running stock COS.
https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Ok. But how can I know if I'm running stock COS (I can't access system settings)?
What I know is that I've bought the phone 3 years ago and done nothing on it (no flash ......) so I think I run an official three years old OPO OS.
So is it a stock COS? (stock OS?)
Thank you for your help.
ziaziung said:
Ok. But how can I know if I'm running stock COS (I can't access system settings)?
What I know is that I've bought the phone 3 years ago and done nothing on it (no flash ......) so I think I run an official three years old OPO OS.
So is it a stock COS? (stock OS?)
Thank you for your help.
Click to expand...
Click to collapse
Ah, so you have the bootloader still locked, which means that to unlock it you would have to factory reset.
You should really backup your stuff and factory reset your phone. I do it once a month or even less.
One more thing I can suggest you is to delete cache, either system app cache or the whole system from the recovery.
Boot to recovery and wipe cache.
Hope it works, if it doesn't I really advise you to factory reset.
COS = CyanogenOS
I'm waiting for my phone to be delivered, and am assuming it will be on Nougat and will upgrade to Oreo when it arrives. Should I factory reset it after the upgrade, or will it be good to go? Can't wait for it to arrive, snowed in at the moment in Ireland!
Anyone? Is there any benefit in doing a factory reset?
I would recommend a factory reset after updating to Oreo can't hurt if there is nothing to lose on the phone.
Just a plain old factory reset then, no wiping cache or anything else?
I'd do a full wipe if you have to lose. When I got mine first I updated through ota, full wipe with Oreo then started to add accounts and apps. Don't think you have to but thought it would be best for to start fresh with Oreo
Misinformation galore!.
You don't need to factory reset after updating unless you experience problems. The updates are approved to not knacker the device.
shivadow said:
Misinformation galore!.
You don't need to factory reset after updating unless you experience problems. The updates are approved to not knacker the device.
Click to expand...
Click to collapse
I actually didn't bother, thought that as it was just out of the box, bit pointless to wipe it.
I agree only wiped as read about issues people had with wakelocks and had nothing to lose as it was just out the box. You are right not really required until you have issues.
I have an unlocked edition S7 that I had put on verizon but has been wifi only for the last few months. I did a factory reset and now it seems that the IMEI is gone? if I dial *#06# I get "SM-g930u is not supported on showimei", and a third party app says imei unknown. Searching on xda I see discussion of people flashing 3rd party firmware and having this outcome, but that's not my situation. My phone has samsung's stock nougat rom on it, never been rooted, etc. Before I go down the odin rabbit hole is there anything else I can try? it seems hard to believe that a factory reset would cause the same kind of failures that incorrectly flashing the ROM would - factory reset shouldn't touch the ROM. Of course anything can happen...
xeosSD said:
I have an unlocked edition S7 that I had put on verizon but has been wifi only for the last few months. I did a factory reset and now it seems that the IMEI is gone? if I dial *#06# I get "SM-g930u is not supported on showimei", and a third party app says imei unknown. Searching on xda I see discussion of people flashing 3rd party firmware and having this outcome, but that's not my situation. My phone has samsung's stock nougat rom on it, never been rooted, etc. Before I go down the odin rabbit hole is there anything else I can try? it seems hard to believe that a factory reset would cause the same kind of failures that incorrectly flashing the ROM would - factory reset shouldn't touch the ROM. Of course anything can happen...
Click to expand...
Click to collapse
Update: seems I managed to update to the oreo OTA by mistake so that's probably the cause, not the factory reset.
xeosSD said:
Update: seems I managed to update to the oreo OTA by mistake so that's probably the cause, not the factory reset.
Click to expand...
Click to collapse
So is the imei still missing? If so factory reset. Something has gone wrong with ota update
cooltt said:
So is the imei still missing? If so factory reset. Something has gone wrong with ota update
Click to expand...
Click to collapse
Yes, it's still missing. I agree, it's the OTA update that must have caused the problem - the factory reset was a red herring.
xeosSD said:
Yes, it's still missing. I agree, it's the OTA update that must have caused the problem - the factory reset was a red herring.
Click to expand...
Click to collapse
So, I've fixed it, using the suggestion of doing a factory reset. So for future posterity: factory reset, then update to oreo, then factory reset again. Silly that it takes doing two resets to get it to work. Meanwhile some shady character tried to sell me octoplus to fix the problem. Beware!
xeosSD said:
So, I've fixed it, using the suggestion of doing a factory reset. So for future posterity: factory reset, then update to oreo, then factory reset again. Silly that it takes doing two resets to get it to work. Meanwhile some shady character tried to sell me octoplus to fix the problem. Beware!
Click to expand...
Click to collapse
Also if you gonna do any mods, back up what you don't want to lose and sign out of Google Account by just deleting it off phone.
You can actually turn off FRP by signing in on a Web browser with Google account and manage device from there.