Related
hi to all.
in the last days i had some errors on my zf2 (ze551ml): too many apps crash continuously so i've do a factory reset.
after that and the first boot asus keyboard continuously crash and many app (google play service, google maps...) crash too. to connect with wifi i need many attemps (one for each character!)
so i tried to flash firware with adb sideload. all done but after reboot same continuously crash as before appears...
i already cleared cache in recovery many times but not helping.
i wad rooted (motode 3, with ota available) but stock and update to 2.20.40.160
how i can fix it?:crying::crying::crying:
What firmware are you on? Have you tried factory reset? Are you stock/rooted/unlocked??
ASUS_Khang said:
What firmware are you on? Have you tried factory reset? Are you stock/rooted/unlocked??
Click to expand...
Click to collapse
already written: firmware 2.20.40.160, rooted, stock
with last flash i think now i'm not rooted but , anyhow, 2.20.40.160
factory reset done some times with a cache wipe before and/or after
ElGato74 said:
already written: firmware 2.20.40.160, rooted, stock
with last flash i think now i'm not rooted but , anyhow, 2.20.40.160
factory reset done some times with a cache wipe before and/or after
Click to expand...
Click to collapse
Yeah tough call, not sure what might be causing it. If you factory reset and get these crashes, then it's not an app problem. Can you run a log of the crashes, or at least describe in detail what's happening when it crashes?
Thanks,
K
well... i don't know how but i fixed it!
i tried many times everything i found in this forum but the solution is (really i thinking, i'm not sure because i have no a list for all attempts) this:
flash last firmware, the same i have previously (v.160 because previous releases stopped during install) with adb sideload
wipe cache
3 times this two passes:
- wipe everything (factory reset)
- reboot in recovery
wipe cache
reboot
thanks anyway for helping me
Hi, I'm aware that several people have issues with the new pie rom.
Unfortunately, I have a problem that I haven't seen before on the forum:
It takes like a full 5 sec to call somebody and the same to end it.
It's very frustrating because I never know how to react in this situation (did he heard? Etc...)
I don't want to factory reset and I got everything stock.
Anyone has an idea on how to fix this?
Can I wipe cache with the stock recovery? Maybe install an other phone app?
Thx
i am having issues in pie as well. i cant seem to transfer large files to the phone.doing so makes the phone restarts. i tried it 5 times or so. fhis update is not good
Only way to clear up issues is a clean factory image install if this was not done to begin with.
OK thanks...
Though I blindfully hope someone will be get some alternative has I don't want do execute such extreme solution
b4bass said:
OK thanks...
Though I blindfully hope someone will be get some alternative has I don't want do execute such extreme solution
Click to expand...
Click to collapse
It's actually relatively painless. Apps restore automatically when you go through setup, calls and texts are restored, as well as system settings and WiFi networks. Takes me ~30 mins total, and maybe 5 of that is actually looking at the phone, the rest is letting it sync and restore backups automatically.
I was thinking about it doing a factory reset once the final came out but I've heard stories from fellow moviepass owners that are unable to use the app when switching phones. That would make a valid concern for factory resets as well. Not because of lag but I have noticed battery seems worse after the upgrade and wanted to factory reset to rule out. As I ran all the ota betas of pie a factory reset isn't a bad idea anyway.
tiny4579 said:
I was thinking about it doing a factory reset once the final came out but I've heard stories from fellow moviepass owners that are unable to use the app when switching phones. That would make a valid concern for factory resets as well. Not because of lag but I have noticed battery seems worse after the upgrade and wanted to factory reset to rule out. As I ran all the ota betas of pie a factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
Your device ID is tied to the app. When you factory reset and reinstall the app your device ID is reset. You can root using Magisk and then install Titanium Backup to backup the app and data, this will preserve the ID. i had to do this when switching ROMS.
I'm running Resurrection Remix and yesterday, when all seemed well, I was browsing on Chrome and the page (Airbnb loading a map of properties...) seemed to overload and crash my phone. It became fully unresponsive and despite waiting a few mins it forced me to hard reset via the power button. It then failed to boot, as it would stay at the boot animation for sometime, boot to recovery and I could see the text "RescueParty" in the TWRP log text.
Unfortunately I could not recover from this. Tried wiping the caches, tried a dirty flash, tried removing magisk and substratum, tried booting into Safe Mode, unfortunately despite all this it failed to boot and went back to recovery, which forced a factory reset of data.
I've reinstalled RR but I guess my question is, had anyone else experienced this and is there a way to somehow fix it without the need for a factory reset? Luckily I could restore my Titanium Backup etc but still means I have to set up all my settings again etc. As I understand, RescueParty attempts to fix errors but boots to recovery as a last hope for the user to factory reset. Clearly something went wrong, but I wonder if it was to happen again, could it be fixed....
cd993 said:
I'm running Resurrection Remix and yesterday, when all seemed well, I was browsing on Chrome and the page (Airbnb loading a map of properties...) seemed to overload and crash my phone. It became fully unresponsive and despite waiting a few mins it forced me to hard reset via the power button. It then failed to boot, as it would stay at the boot animation for sometime, boot to recovery and I could see the text "RescueParty" in the TWRP log text.
Unfortunately I could not recover from this. Tried wiping the caches, tried a dirty flash, tried removing magisk and substratum, tried booting into Safe Mode, unfortunately despite all this it failed to boot and went back to recovery, which forced a factory reset of data.
I've reinstalled RR but I guess my question is, had anyone else experienced this and is there a way to somehow fix it without the need for a factory reset? Luckily I could restore my Titanium Backup etc but still means I have to set up all my settings again etc. As I understand, RescueParty attempts to fix errors but boots to recovery as a last hope for the user to factory reset. Clearly something went wrong, but I wonder if it was to happen again, could it be fixed....
Click to expand...
Click to collapse
It could be kernel panic due to lmk commits
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
It could be kernel panic due to lmk commits
Click to expand...
Click to collapse
Good shout.
I was hopeful that a dirty flash would have helped but its like something got corrupt in the data somewhere as clearing caches didn't help.
cd993 said:
Good shout.
I was hopeful that a dirty flash would have helped but its like something got corrupt in the data somewhere as clearing caches didn't help.
Click to expand...
Click to collapse
I just installed rr yesterday
And i am having very slow fingerprint unlock, are you facing the same? Mine takes almost about 2 sec or so
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
I just installed rr yesterday
And i am having very slow fingerprint unlock, are you facing the same? Mine takes almost about 2 sec or so
Click to expand...
Click to collapse
Hmm not for me I'm afraid, fingerprint is as fast as normal with no delays. I'm using the kernel it comes with (a slightly modified Flash kernel I believe)
cd993 said:
Hmm not for me I'm afraid, fingerprint is as fast as normal with no delays. I'm using the kernel it comes with (a slightly modified Flash kernel I believe)
Click to expand...
Click to collapse
I'm using the flash kernel by nathan never tested it on stock Kernel but stock Kernel has lmk commits which cause freezes for me
Sent from my Google Pixel 2 XL using XDA Labs
My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
- Both issues linger in safe mode.
Any ideas on wtf could be going on?
boeder9 said:
My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
Any ideas on wtf could be going on?
Click to expand...
Click to collapse
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.
Badger50 said:
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.
Click to expand...
Click to collapse
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?
boeder9 said:
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?
Click to expand...
Click to collapse
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:
Badger50 said:
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:
Click to expand...
Click to collapse
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Sent from my Pixel 2 XL using Tapatalk
boeder9 said:
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Click to expand...
Click to collapse
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs
Even i have the same camera issue. It suddenly stopped working. Some times it does start after a few tries if i hold it in landscape mode. But mostly it keeps crashing and doesn't even allow other apps to access camera.
So a quick follow-up. Here is what i've done so far:
- Cleared storage/cache and uninstalled the camera updates
- Installed Android 10
- Updated to Camera 7.0 Beta
- Booted into safe mode.
None of these actions solved the issue.
I then resetted my phone (2 days ago) and that seemed to have solved the problem. However, starting a few minutes ago and while I was taking photos, I again lost focus in the lens and the app crashed.
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.
boeder9 said:
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.
Click to expand...
Click to collapse
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.
Strephon Alkhalikoi said:
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.
Click to expand...
Click to collapse
You're absolutely right. I did another reset (this time without restoring from backup) and the camera doesn't open at all. I'm hoping its a OS bug.
Thank god the Pixel 4 will be released in 4 weeks.
CyberpodS2 said:
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I have exactly the same problem that they report, it does not open cameras or YouTube.
Can you give me the steps to upload a factory image?
Regards
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.