So, something pretty strange just happened. Earlier today I downloaded the latest OTA to my phone to flash with TWRP sometime in the next few days. I was playing around with my phone tonight and setting up Google Assistant to work with my Nest thermostat. The Assistant wasn't consistently recognizing the ability to adjust my thermostat so I did a simple reboot thinking it may solidify things. Much to my surprise, when I rebooted the phone, I noticed the Nougat 'N' in the status bar and when I pulled down the notification drawer it said "finishing upgrade," or something to that effect. STRANGE. I figured, surely my phone didn't just update on its own, so I checked about device and surely I'm on the latest build. Went to reboot my phone and TWRP was replaced with the factory recover and I no longer have root.
In the end, I have no idea how this happened. Everything I have read says updates will fail with a modified system and in fact I've tried updating in the past only to have it fail. Any ideas How or why this happened?
You got a real SMARTPHONE!
mlin said:
Everything I have read says updates will fail with a modified system and in fact I've tried updating in the past only to have it fail. Any ideas How or why this happened?
Click to expand...
Click to collapse
While I can't explain how this happened, I can point out that recovery is part of the boot image. And SuperSU is a "systemless" root method that also modifies the boot image. So your system image would appear as stock.
Sounds very interesting... I hope someone could answer this.
FlashFire? Also, do you have auto-update disabled in developer settings?
i got mine not long ago and had 7.1 on it and i did root and added twrp and in the background it downloaded 7.1.1 and when i did a reboot it installed it with no issue.
turn off auto update
sliding_billy said:
FlashFire? Also, do you have auto-update disabled in developer settings?
Click to expand...
Click to collapse
Thanks for all of the responses. No flashfire. Auto update was on. I thought it was weird that with root, custom recovery and substratum theming that my phone updated, especially given the fact that I have tried to update several times through the system updates menu and it has always failed... No clue why it suddenly worked, and furthermore why it happened out of the blue.
mlin said:
Thanks for all of the responses. No flashfire. Auto update was on. I thought it was weird that with root, custom recovery and substratum theming that my phone updated, especially given the fact that I have tried to update several times through the system updates menu and it has always failed... No clue why it suddenly worked, and furthermore why it happened out of the blue.
Click to expand...
Click to collapse
Purely hypothesis, but this update seemed to touch very few core system files and maybe just by luck none of what normally would cause it to fail was checked for changes. Recovery seems to be it's own animal as running TWRP sideload just wipes all recovery. In your case it replaced it with stock since you ran basically a standard OTA.
fletch33 said:
i got mine not long ago and had 7.1 on it and i did root and added twrp and in the background it downloaded 7.1.1 and when i did a reboot it installed it with no issue.
Click to expand...
Click to collapse
Yeah, I knew TWRP alone wouldn't interfere with the update, but I thought root and other mods would. This is why I wasn't surprised when trying to update previously failed but was super surprised when it suddenly worked.
Apparently my wife's Pixel did this today as well. She said she didn't ever see anything about an update.
Its a Verizon model but was rooted, bootloader unlocked, with twrp installed.
It was previously on the December update just like my Pixel XL, but now is on February.
It currently won't make calls or record video, which is why she even asked me about it. I started working on it and noticed it was no longer rooted or had TWRP. I just got those two back and now have to try to get calls working.
jsbeagle said:
Apparently my wife's Pixel did this today as well. She said she didn't ever see anything about an update.
Its a Verizon model but was rooted, bootloader unlocked, with twrp installed.
It was previously on the December update just like my Pixel XL, but now is on February.
It currently won't make calls or record video, which is why she even asked me about it. I started working on it and noticed it was no longer rooted or had TWRP. I just got those two back and now have to try to get calls working.
Click to expand...
Click to collapse
Interesting, I was on the December update as well. No problems with calls or video though. Very strange that in 2 months the January patch never successfully applied but the February patch did. Good luck with calls and video.
A full factory image flash got everything working. It kept working after installing TWRP, but after I root (SuperSU v2.79 SR3) it stops again.
jsbeagle said:
A full factory image flash got everything working. It kept working after installing TWRP, but after I root (SuperSU v2.79 SR3) it stops again.
Click to expand...
Click to collapse
What stops again?
I am on 7.1.2 Beta and everything works good.
Whats not working for you?
After I root, the phone app gets sluggish, phone call audio doesn't work, the camera app "can't connect to camera" if you try switching to video, and youtube videos don't work in the app. They worked in the browser but had no audio.
jsbeagle said:
After I root, the phone app gets sluggish, phone call audio doesn't work, the camera app "can't connect to camera" if you try switching to video, and youtube videos don't work in the app. They worked in the browser but had no audio.
Click to expand...
Click to collapse
Granted, after I got the update everything seemed a bit smoother. Audio seemed louder and more crisp.
Have you tried a factory reset?
Scott said:
What stops again?
I am on 7.1.2 Beta and everything works good.
Whats not working for you?
Click to expand...
Click to collapse
Well, I guess its not even related to rooting. I had reflashed factory 7.1.1, installed twrp, and everything was still working. After I installed a few apps and restarted, all that stuff's not working again.
It doesn't even work in safe mode.
Just did a factory reset and it didn't help.
jsbeagle said:
Well, I guess its not even related to rooting. I had reflashed factory 7.1.1, installed twrp, and everything was still working. After I installed a few apps and restarted, all that stuff's not working again.
It doesn't even work in safe mode.
Click to expand...
Click to collapse
Thats really odd. Maybe its an app thats not updated for 7.1.1.
I would reflash, let it wipe, then run it as a new phone for 24hrs. If it runs fine then I would install only essential apps, one by one and test after each one. Your sure to find the rotten apple that way. :good:
Good luck!
Related
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
andygold said:
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
Click to expand...
Click to collapse
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
wildbean98 said:
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
Click to expand...
Click to collapse
I took the update against my better judgement and sure enough soft bricked and now phone wont go into DL mode...grrrr
Major issues here as well. My SD card is now blank and doesn't want to mount. Big slowdowns as well. Any way to remove this update ?
Sent from my SHIELD Tablet using Tapatalk
Was finally able to DL apps, but at a crawl. I cleared the cache including dalvik, and everything is back to normal. And I'm still rooted!
I used Cache Cleaner NG from the play store
Soft bricked
I have bricked my phone after accidentally accepting it. Got back the phone again with lg flash tool. Once restarted the phone, rooted it, used titanium backup apk to freeze the software updater.
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Actually guys, its most likely that malware piece that was making its way around. Didnt anyone else read about it a few days ago? Let me hunt it down and see if i can post a link here. Standby....
Update: hold the phone, i may have been mistaken. Standby...
Now im soo broke i cant even pay attention!
ThaHawk said:
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Click to expand...
Click to collapse
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
sdivk said:
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
Click to expand...
Click to collapse
I stand corrected, your absolutely right!
ThaHawk said:
I stand corrected, your absolutely right!
Click to expand...
Click to collapse
Thanks. If you have a rooted lg e980 without custom recovery, you can use quickboot apk to enter stock recovery, which has limited features.
The problem with unlocking bootloader and use custom recovery is, if there is an update, there is no way to relock the bootloader and flash stock recovery. If sombody can shed the light on this matter, i really appreciate it.
I am looking for a way to relock the bootloader and install stock recovery without using lg flash tool.
Not that i am expecting an update from AT&T anytime soon.
+1
its better its included on CM based ROMs also
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
baronimus said:
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
Click to expand...
Click to collapse
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
golfnut22 said:
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
Click to expand...
Click to collapse
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
baronimus said:
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
Click to expand...
Click to collapse
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
golfnut22 said:
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
Click to expand...
Click to collapse
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
baronimus said:
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
Click to expand...
Click to collapse
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
golfnut22 said:
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
Click to expand...
Click to collapse
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
baronimus said:
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
Click to expand...
Click to collapse
I may have stopped updating one to early. Anyway, my watch updated by itself last night all the way to MM, now it is stuck again. I'll have to search and see if there is a way to stop the automatic OTA updates.
I have seen where people have flashed only the kernel. I have not. At this point, it would be nice just to keep it at the last LP. I'll let you know if I find anything. Thanks.
I have a mate SE (BND-L34) that was on 8.0. Back in September of 2018, I unlocked it and rooted using another thread in this forum. All was working fine until a few days ago when I tried to install xposed using magisk. That bricked the phone. TWRP came up but boot looped. Finally got to the point where my only option was to let it download a stock image through wifi. I did, and then it had a couple updates available, and I let it update to build number BND-L34 8.0.0.352(C567). It also shows android security patch of February 1, 2019. That took the phone back to completely stock. All data wiped, no unlocked warning at bootup.
correction: At bootup, it does still give me the unlocked warning.
So anyway, All seemed to be working and I could add fingers to the list and they will unlock the phone fine. Then I installed an app that could use the fingerprint to unlock it, and I found that it did not work at all. The app waits for the fingerprint to be detected and it never happens. So I tried a different app, and same thing, just waits for the detect to happen. Again, the finger print unlocks the phone without hesitation, every time.
This makes me think that one of the updates is causing a problem. I've done some searching both on xda and google, and come up with nothing. Like no one else has seen this problem.
So I have a few questions:
1) Has anyone else seen this problem?
2) Can I use firmware finder to install a previous build, like the one from January or even the one from September? I don't have TWRP or root, just the stock image.
3) If I can't use firmware finder to downgrade, is there another way? Like through adb or something.
update:
Here's the answer to questions 2 & 3 above:
I was able to use firmware finder to download the January build .351. I couldn't get firmware finder to flash it. I then installed twrp into recovery using the image I found here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500. I followed the steps in this post https://forum.xda-developers.com/honor-7x/how-to/tested-unbrick-bnd-l24-t3811645 to flash the .351 image. I just used the files I downloaded from firmware finder instead of the ones list there.
And since no one has replied, I'm guessing that this problem is mine alone. Also, going back to 8.0.0.351 did not solve the problem.
I finally rolled all the way back to 8.0.0.344(C567) (first Oreo, I think, from September) and now the fingerprint sensor works for applications. I have no idea why. Maybe there was a security update in the Jan build that disabled the fingerprint if the phone was unlocked. But it seems unlikely since no one else saw the same problem. I can't be the only person with an unlocked BND-L34 that let the phone update to the latest ota.
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Delete
electric bill said:
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Click to expand...
Click to collapse
Yeah, I posted the same thing a month or so ago and ended up figuring it out. Since you are rooted, the same solution I used will work for you. Froze the EMUI System Update process with Titanium Backup.
https://forum.xda-developers.com/hon...ation-t3897144
Welp
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
electric bill said:
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
Click to expand...
Click to collapse
it's a problem with the app. If I restore an older version with titanium, it works fine.
Hi, I unlocked my mate SE boot-loader and rooted it. After upgrading to BND-L34 8.0.0.352, My TWRP disappeared and lost root. I tried used fastboot to reflash TWRP and failed. Could you confirm if your TWRP worked on version 352? Even I reverted my rom back to 344 using "Firmware finder", I still could not install custom any recovery. Could you help?
Good evening,
So I decided to finally root my Pixel 3 XL.
After successfully rooting it with magisk, I've notice all the time now that when I receive a notification regularly it mutes whatever I'm watching. YouTube vids, videos or any media I'm looking at.
But the thing is it doesn't unmute after. It stays muted until I go home or close it and re watch it.
This has never happened to me before and it started happening right after I rooted my phone.
Stock rom and haven't installed any mods.
I did install viper4android to see if it'll fix it, but nothing.
Has anyone had this issue ?
Thanks in advance.
Btw I tried unrooting and doing everything over again and still same issue.
GunToYoMouth123 said:
Good evening,
So I decided to finally root my Pixel 3 XL.
After successfully rooting it with magisk, I've notice all the time now that when I receive a notification regularly it mutes whatever I'm watching. YouTube vids, videos or any media I'm looking at.
But the thing is it doesn't unmute after. It stays muted until I go home or close it and re watch it.
This has never happened to me before and it started happening right after I rooted my phone.
Stock rom and haven't installed any mods.
I did install viper4android to see if it'll fix it, but nothing.
Has anyone had this issue ?
Thanks in advance.
Btw I tried unrooting and doing everything over again and still same issue.
Click to expand...
Click to collapse
I have the same issue
GunToYoMouth123 said:
Good evening,
So I decided to finally root my Pixel 3 XL.
After successfully rooting it with magisk, I've notice all the time now that when I receive a notification regularly it mutes whatever I'm watching. YouTube vids, videos or any media I'm looking at.
But the thing is it doesn't unmute after. It stays muted until I go home or close it and re watch it.
This has never happened to me before and it started happening right after I rooted my phone.
Stock rom and haven't installed any mods.
I did install viper4android to see if it'll fix it, but nothing.
Has anyone had this issue ?
Thanks in advance. Btw I tried unrooting and doing everything over again and still same issue.
Click to expand...
Click to collapse
Very odd...first time I've heard of this. So un-rooting solves it? Reapplying root then breaks it again? Can you duplicate this running in safe mode, or not? It may indicate whether another app you have installed is causing the problem. Another (albeit a longshot) thing to try would be to reset app settings under System>>Reset options. Does not delete any app data. Lastly, I don't know how you guys update monthly (ota vs image) but I would fastboot flash the latest full image removing the -w wipe switch from the flash-all script. Fastboot boot TWRP and flash the latest magisk.zip file from there. Let us know how you get on.
GunToYoMouth123 said:
Good evening,
So I decided to finally root my Pixel 3 XL.
After successfully rooting it with magisk, I've notice all the time now that when I receive a notification regularly it mutes whatever I'm watching. YouTube vids, videos or any media I'm looking at.
But the thing is it doesn't unmute after. It stays muted until I go home or close it and re watch it.
This has never happened to me before and it started happening right after I rooted my phone.
Stock rom and haven't installed any mods.
I did install viper4android to see if it'll fix it, but nothing.
Has anyone had this issue ?
Thanks in advance.
Btw I tried unrooting and doing everything over again and still same issue.
Click to expand...
Click to collapse
I experienced it after the Feb OTA.
https://forum.xda-developers.com/pixel-3-xl/help/youtube-feb-ota-audio-feed-mysteriously-t3897843
I dont know why or how but it has gone away.
I am on current patch, magisk beta, stock rom.
v12xke said:
Very odd...first time I've heard of this. So un-rooting solves it? Reapplying root then breaks it again? Can you duplicate this running in safe mode, or not? It may indicate whether another app you have installed is causing the problem. Another (albeit a longshot) thing to try would be to reset app settings under System>>Reset options. Does not delete any app data. Lastly, I don't know how you guys update monthly (ota vs image) but I would fastboot flash the latest full image removing the -w wipe switch from the flash-all script. Fastboot boot TWRP and flash the latest magisk.zip file from there. Let us know how you get on.
Click to expand...
Click to collapse
Thank you for the quick reply. I'll give it shot when I get home.
I haven't updated my phone at all, it's on the March update.
But yes, it seems as if the issue only occurred once I rooted it with magisk.
Fastboot flash the lasted update and then fast boot into TWRP the lasted magisk.zip over what I have without wiping correct ?
I believe the latest stock is the newly April update ending with .003
parakleet said:
I experienced it after the Feb OTA.
https://forum.xda-developers.com/pixel-3-xl/help/youtube-feb-ota-audio-feed-mysteriously-t3897843
I dont know why or how but it has gone away.
I am on current patch, magisk beta, stock rom.
Click to expand...
Click to collapse
What sick are you running? March update .002 or April update .003?
And how do you update your firmware ?
GunToYoMouth123 said:
Thank you for the quick reply. I'll give it shot when I get home.
I haven't updated my phone at all, it's on the March update.
But yes, it seems as if the issue only occurred once I rooted it with magisk.
Fastboot flash the lasted update and then fast boot into TWRP the lasted magisk.zip over what I have without wiping correct ?
I believe the latest stock is the newly April update ending with .003
Click to expand...
Click to collapse
Since you haven't updated to April yet, now is a good time to flash the full image. Open the image file and extract all it's contents into your adb folder. Please make sure you are using the latest fastboot/adb binaries HERE. Open the flash-all.bat file with notepad and edit removing the "-w" from the script and make sure you save before closing. This will make sure that you will not lose any data. Now just execute the script. You can do this by clicking on it, or from the command line. Once completed, "fastboot boot twrp.img" (not the zip). Use TWRP to install the latest magisk.zip which you should place on the phone before starting. Good luck!
For me this issue appears only with audio mods like viper/Ainur/JamesDSP, without it everything works... I think big G change something in the last update
GunToYoMouth123 said:
What sick are you running? March update .002 or April update .003?
And how do you update your firmware ?
Click to expand...
Click to collapse
I am on the current Apr patch.
Just flashed the OTA like always nothing special.
v12xke said:
Since you haven't updated to April yet, now is a good time to flash the full image. Open the image file and extract all it's contents into your adb folder. Please make sure you are using the latest fastboot/adb binaries HERE. Open the flash-all.bat file with notepad and edit removing the "-w" from the script and make sure you save before closing. This will make sure that you will not lose any data. Now just execute the script. You can do this by clicking on it, or from the command line. Once completed, "fastboot boot twrp.img" (not the zip). Use TWRP to install the latest magisk.zip which you should place on the phone before starting. Good luck!
Click to expand...
Click to collapse
Doing this will ease my system and storage?
Just want to make sure. Thank you.
GunToYoMouth123 said:
Doing this will ease my system and storage?
Just want to make sure. Thank you.
Click to expand...
Click to collapse
It will wipe your system and other partitions but will not wipe /data/media (your storage). Obviously you will lose TWRP recovery.
oh **** thought i was the only one
With acp + aml audio mods works again (ainur + James DSP) , but the audio will crackling and popping... I've to try without ainur and or with viper, I'll let u know
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.