Related
Hi. I downloaded Lollipop but have not installed it yet and don't want to. I didn't know it was Lollipop I was downloading. How do I get rid of the possibility of it installing? I keep having to delay it for 24 hours. Do I have to do a factory data reset?
What version of anroud are you on and are you rooted? If so you can simply go to the /cache folder and delete the .cfg file file.
If you reboot before doing that the update will be installed.
I'm on 4.4.2 and not rooted. If I do a factory data reset before I install Lollipop would that get rid of the download ?
"Luke" don't fight it, grab the lollipop and feel the Force.
The force never tasted better.
Pp.
What is your reason for not wanting to update? Anything particular?
Rhino_7 said:
I'm on 4.4.2 and not rooted. If I do a factory data reset before I install Lollipop would that get rid of the download ?
Click to expand...
Click to collapse
From what I know , when you try a factory reset it will reboot your phone to recovery and perform the reset there. It may successfully do so, or it may immediately install the update in recovery. I can't say for sure.
If it is absolutely necessary for you to avoid this update, backup your files, download a firmware from Sammobile that matches your current 4.4.2, very carefully reset to download mode (you will only have one shot at this) and Odin that old firmware into your system. Hopefully that will overwrite all your files and remove the update. On the first boot enter recovery and do a reset. That is the most likely solution I can think of which may have a remote chance of working.
Another possibility is that if your firmware has a date before Jun 5 2014, you can run towel root version 3 to root it (doesn't require a reboot) then go to the cache directory and delete the update file. Of course all of this should be done before rebooting. This should work but you will end up with a rooted system.
Finally if your were forced to take the update you can almost downgrade it back to 4.4.2.
Thanks. I just did a factory data reset and it worked fine.
The reason is I like the phone now just as it is. No WiFi issues,great battery life,ect. From what i have read even though Lollipop is a big update there is nothing new that makes me want to have it.
Anyone want to try and convince me?
Android updates seem to always be buggy. I "might" try it later.
I went straight up Kies update and the phone never ran smoother.
Running stock /rooted / debloated and everything works the way it's supposed to.
No bells, no whistles, no exposed, just straight up touchwiz.
Knox shmox, never gave it a second thought after the warranty ran out.
Pp.
This has been my biggest problem with my OP3 and OOS. I want to be able to safely dirty flash my rom without losing data.
Im a long time Android power user. CyanogenMod would always be a nice easy upgrade to the latest version. Dirty unicorns, albeit buggy on my Oppo Find 7, would upgrade easily.
The last time I tried an OTA update, it trashed all my data and settings. Subsequent updates have been major upgrades (updating kernels. Major changes like OOS 3.X to 4.X. etc etc), so I haven't tried doing a OTA/Dirty flash in a while. I have been cautious since the data wipe last time.
Any advice on how I can do an OTA easily and safely?
I have TWRP. I'm UNrooted and on OOS 4.1.1.
Backup everything.. Wipe system flash 4.1.1 and it should be fine, if not restore your back up. System does not contain any data nor settings.
Ok. Will it work with the 4.1.6 OTA I got? Or should I download the full room from the website
You have to download the full zip if you have TWRP installed. You can't update via ota.
I would recommend a TWRP backup and system, cache/dalvic wipe too.
Gucci! Thanks fam
ssjaken said:
Gucci! Thanks fam
Click to expand...
Click to collapse
Well, you know, I had the same issue with my wife's 3T. Was terrible (and lucky), right out of the box, try to upgrade like you want to do, and the update would fail in the middle, requiring to wipe the phone to have it boot.
Luckily, as I said, the phone was new like 5 minutes old. I don't imagine what would happen after a few months use.
What I did to make it work was to use the stock recovery to flash the full rom zip from OP servers, and that worked.
All subsequent updates went well (with a little bit of stress we all know : will it boot, won't it? and if it does not, will I keep my head?)
Haha. Of course, you must be on stock recovery to do so, but it's easy to do, just follow the official way to do it "manually".
Oh, and backup all your stuff
Hi,
am using a Pixel XL 1 on Android 8.1, bootloader unlocked, patch level of February. Now I have the problem that since about December no OTA updates are shown/offered at all. Therefor I always had to manually update.
Even the manual triggering of searching for updates, which has recently been changed so that the devices explicitly should get the currently available update, does not work.
The device was rooted, but I have unrooted it (Magisk) now, and is running the standard firmware from Feburar on it.
Does anyone have any clue why my device is not offered any OTA updates?
Anyone?
What kind of recovery do you have installed? Stock or TWRP?
Kream24 said:
What kind of recovery do you have installed? Stock or TWRP?
Click to expand...
Click to collapse
Stock. So everything should be as vanilla as possible! I'm really clueless.
i don't get it either. pixels running a non-stock os should get notifications about a new update. they won't install successfully though. i'm guessing, but maybe going through the unroot process to get rid of magisk did not return your os to completely stock. maybe some junk was left behind and that's causing your issue.
my suggestion is to flash a full factory image to start fresh. i would edit the flash-all.bat script to remove the -w option to keep data. if that doesn't work, put the -w option back and rerun to wipe data and flash the factory image. if you really want to see if that fixes your problem, flash an older image like the february or january one, and see if the update notification comes back. or flash the march image to be up to date and wait until april to see if you get the update notification.
altwu said:
i don't get it either. pixels running a non-stock os should get notifications about a new update. they won't install successfully though. i'm guessing, but maybe going through the unroot process to get rid of magisk did not return your os to completely stock. maybe some junk was left behind and that's causing your issue.
my suggestion is to flash a full factory image to start fresh. i would edit the flash-all.bat script to remove the -w option to keep data.
Click to expand...
Click to collapse
That's what I've did already No difference.
if that doesn't work, put the -w option back and rerun to wipe data and flash the factory image.
Click to expand...
Click to collapse
It's just the hassle installing everything from scratch again.
I wish recovery/backup was as easy as on iOS. Without necessity of any tricks, root etc.
Is this phone enrolled in the Android Beta Program ? I've had trouble getting OTA updates on my phone after the beta program ended for it until I un-enrolled from the program, then I got updates like normal. There will be warnings about having to wipe the device, but if your on the the stock/stable version already you won't have to.
shaneledford said:
Is this phone enrolled in the Android Beta Program ? I've had trouble getting OTA updates on my phone after the beta program ended for it until I un-enrolled from the program, then I got updates like normal. There will be warnings about having to wipe the device, but if your on the the stock/stable version already you won't have to.
Click to expand...
Click to collapse
Tried that one as well. I was on a beta at some point, but unsubscribed from the beta. Also tried to unsubscribe again, but it the well know link took me to a page where it said that there is no beta, hence I couldn't try to unsubscribe again.
When you flashed the full factory image did you use the newest march update? if you did then you wouldnt get anything because you are already current
Gotta say, exactly the same problem.. stuck on 8.0 November lol. Haven't found a solution, too lazy to manually flash for now. Let me know if you find a solution!
have you tried deleting the data and cache on the google services app?
Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.
is it worth factory resetting device with this latest update?
Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.
jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.
bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?
animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.
Hi all,
I am learning so much during these days about CSC and what it is and what is not.
My phone was purchased in Personal (Argentina cellphone company) and it came with OWX firmware (PSN is the code of the company). After one month i changed it to multi-csc OWO (and the default CSC for that rom is ZTO (brazil)), so my phone change to Brasil region (model in phone info app shows N975FZSMZTO and in the box say N975FZSMPSN). Then I always update using Odin to OWO multi-csc rom (using BVO or ZTO or ARO) but the phone always stays at ZTO (not a problem for me, never realize till now).
In software version my phone shows ZTO/ZTO/PSN (i assume the last one is the carrier config? not sure why or how the combination is like that as PSN is not included in OWO multi-csc ROM).
I have alwat updated software via odin using HOME_CSC file and never have a problem till now.
The fact is that the last update (one ui 2.1) appear and i accepted in my phone (not using odin) and after it get installed, the day after, the phone start crashing, rebooting, not working, unstable, horrible!. I have already tried everything, flashing again the multi-csc OWO using oding, use the CSC file instead of the HOME_CSC and also rolling back to one ui 2.0 (PDA BTB9), but it drives me crazy as it won't stop rebooting. The fun fact is that the phone works perfectly last time (for 5 days) and now again this monday morning (near 2.30 AM) start rebooting. It looks like it start rebooting always on monday at the same time till something stop it (firmware flash, whatever).
I have stopped the device care auto optimization, stop the synch options, almost all is tried and no result, phone won't stop rebooting. It start the bootloop for about 10 minutes (like 1 reboot per minute) and then it calm down till next day.
I am now waiting for my company Personal to release the new firmware version (one ui 2.1) to flash back that CSC OWX (PSN) version.
My question is, if i change from the multi-csc to the OWX csc, will it effectively change backa again its original CSC? As that rom is not multi-csc, probably it will work? Also, can i change to another CSC firmware (in this case switch back to OWX) using home_csc to avoid wipe or will it cause troubles too?
My thought is that after the automatic update from the network (not using odin) something in the CSC or settings got broken or mixed. So this is why i want to try to go back to the PSN.
Also i have already performed like 4 or 5 factory resets, nothing works now.
Hope somebody can help me as it really don't look as hardware problem, but software.
Thanks for the time in advance!!
Yamil
Have you tried flashing the multi csc rom with ODIN?
Can't hurt...
ultramag69 said:
Have you tried flashing the multi csc rom with ODIN?
Can't hurt...
Click to expand...
Click to collapse
Yes, i have tried it. Actually i am using the BTB9 multi-csc flashed with odin and it reboots again and again yesterday. Todas is not doing it, i have stopped all synch things and also removed apps inside secure folder, that i use as a second space to work. I detected that when i receive messages or calls in Microsoft teams inside secure folder, it reboots.
I am testing and testing. Today PSN (OWX CSC) release the new version so i will flash it and start from 0 again and continue verifying.
I'm not sure but could it be something broken in /system partition? I was thinking to delete that patition but i will need TWRP and that wil trigger knox. If i flash a firmware using odin, will that erase that partition and put the system from 0 or it keeps some files?
yamwt said:
Yes, i have tried it. Actually i am using the BTB9 multi-csc flashed with odin and it reboots again and again yesterday. Todas is not doing it, i have stopped all synch things and also removed apps inside secure folder, that i use as a second space to work. I detected that when i receive messages or calls in Microsoft teams inside secure folder, it reboots.
I am testing and testing. Today PSN (OWX CSC) release the new version so i will flash it and start from 0 again and continue verifying.
I'm not sure but could it be something broken in /system partition? I was thinking to delete that patition but i will need TWRP and that wil trigger knox. If i flash a firmware using odin, will that erase that partition and put the system from 0 or it keeps some files?
Click to expand...
Click to collapse
I'm not sure what could be causing it as once you flash with ODIN it pretty much wipes the device of all system files and the OS thereby giving a clean install...
OTA on the other hand just updates the System and OS as needed... This is why a fresh install is the suggested method over OTA if there is a problem...
If you haven't rooted the phone I would consider re-flashing the stock rom, if this doesn't work then take it back for a warranty repair as this should not be happening only 6 months after you got it...
ultramag69 said:
I'm not sure what could be causing it as once you flash with ODIN it pretty much wipes the device of all system files and the OS thereby giving a clean install...
OTA on the other hand just updates the System and OS as needed... This is why a fresh install is the suggested method over OTA if there is a problem...
If you haven't rooted the phone I would consider re-flashing the stock rom, if this doesn't work then take it back for a warranty repair as this should not be happening only 6 months after you got it...
Click to expand...
Click to collapse
Hey there,
Yes, yesterday i have reflashed the CSC stock (PSN) that launched the 2.1 version, clean and super clean install (phone erased from recovery before flashing and after too). The CSC default from that OWX is CHT (Chile) so now i have it set for chile, lol. It includes PSN but i assume i will need to pay samkey to change it or root (and i will not root till warranty ends).
It is working fine at least for now, 24 hours without problem. The fun fact is that the "problem" appears after few days, last 2 times it happen on a monday during the night (this is why i thikn this is not hardware but software). But if this happen agin, there is nothing else to do to software level and i will need to claim warranty
Regards,