At all, Nexus 5x sensors not working. - Nexus 5X Q&A, Help & Troubleshooting

I signed up for goolge android beta program. After upgrading to android 8 beta 4, I noticed auto rotation and all sensors don't work anywhere, I've wiped all the phone ( system, internal storage, dalvik and cache) and installed the latest factory image but the problem doesn't seem to solve.
I am currently in the latest android version 7.1.2 with all unresolved issues.
Any solution? Thanks!

Did you reflash stock with full wipe? If you did, try a factory reset as well.

I am having this issue as well
morebube said:
I signed up for goolge android beta program. After upgrading to android 8 beta 4, I noticed auto rotation and all sensors don't work anywhere, I've wiped all the phone ( system, internal storage, dalvik and cache) and installed the latest factory image but the problem doesn't seem to solve.
I am currently in the latest android version 7.1.2 with all unresolved issues.
Any solution? Thanks!
Click to expand...
Click to collapse
I have the same issue, Until now I was thinking my hardware fryed, cz a few weeks back I had to clean the board because of water damage.Immediatly After that, I've opted-out of beta and suddenly all the sensors (Gyro, Pedometer, Light, Magnetic etc.) stopped working, And I blamed it on the hardware. I will wipe the device try a custom ROM or something and will update this thread:good:
Also check this issue reported in Google Product forum, It seems it can be fixed by a wipe
https://productforums.google.com/forum/#!topic/nexus/o3HT7MgKQbY;context-place=topicsearchin/nexus/nexus$205x

i.adrian said:
Did you reflash stock with full wipe? If you did, try a factory reset as well.
Click to expand...
Click to collapse
I did it all.
Factory reset, wipe in recovery, flash stock image... But can not fix.

I've had the same issue at one time. Can't remember the exact steps, but I think I flashed stock with fullwipe of the device and locked my bootloader. You could try. But first try and flash the vendor image.

i.adrian said:
I've had the same issue at one time. Can't remember the exact steps, but I think I flashed stock with fullwipe of the device and locked my bootloader. You could try. But first try and flash the vendor image.
Click to expand...
Click to collapse
I flashed stock with fullwipe of the device and locked my bootloader. I am currently in the latest android version 7.1.2.
Which vendor i need?

Re-enroll to beta and update
Since I could not afford to lose the data and I am too lazy to sign in to all the applications, I did not wipe the Phone, I just re-enrolled to beta program again and updated the OS to Android O beta. And now, everything seems to work now. Thank you for opening this thread I would have never found out it was a driver issue if it wasn't for you

On nougat,I solved it by re-lock bootloader

linckandrea said:
On nougat,I solved it by re-lock bootloader
Click to expand...
Click to collapse
I did that a hundred times in vain.

Just press firmly on the cover in all places. Resolved my issue with the sensors!

Related

custom rom, can't start phone because all apps keep stopping

I hab ic 12.0.1 running perfectly on my phone. I flashed 12.1.0 over it without a wipe and it worked perfectly. I then thougt why not full wipe it with the 12.1.0 and have fresh start? Thats when the problems began. Twitter Facebook and a bunch of other apps kept fc. Then i thought i install another rom. the maximus 8. WIth that Rom i couldn't even complete the process where you set up your phone because everything kept restarting. even the gapps. i reloccked and locked my bootloader, i flashed everything with a tool, i even tried the firmware update tool again ( i'm on Hboot 1.31) , i flashed the boot.img manually. and i cant get any rom working. i don't know what to do?
daria55 said:
I hab ic 12.0.1 running perfectly on my phone. I flashed 12.1.0 over it without a wipe and it worked perfectly. I then thougt why not full wipe it with the 12.1.0 and have fresh start? Thats when the problems began. Twitter Facebook and a bunch of other apps kept fc. Then i thought i install another rom. the maximus 8. WIth that Rom i couldn't even complete the process where you set up your phone because everything kept restarting. even the gapps. i reloccked and locked my bootloader, i flashed everything with a tool, i even tried the firmware update tool again ( i'm on Hboot 1.31) , i flashed the boot.img manually. and i cant get any rom working. i don't know what to do?
Click to expand...
Click to collapse
did you flash their boot.img??
matt95 said:
did you flash their boot.img??
Click to expand...
Click to collapse
of course. with various methods. it seems that the prgramms can't write, or mount on one particular. but i'm really out of ideas. i don't know how to fix this. the only thing i would do next is a ruu. but because of the hboot 1.31 there is no ruu available.
the weirdest thing happend. it seems to be working again. i switsched back to cwtr. wiped everything. and did a clean install with a full wipe with ic 12.2.2 so far no issues. weird thing. because thats the same thing i did the last 2 days.
daria55 said:
the weirdest thing happend. it seems to be working again. i switsched back to cwtr. wiped everything. and did a clean install with a full wipe with ic 12.2.2 so far no issues. weird thing. because thats the same thing i did the last 2 days.
Click to expand...
Click to collapse
DAMNIT! after 3 min in the system it starts again with the force closes!
daria55 said:
DAMNIT! after 3 min in the system it starts again with the force closes!
Click to expand...
Click to collapse
are these ROMs meant to work with hboot 1.31? i know ARHD14.2 works.
try that rom. clean wipe and no other add.ons first
after more searching i came across this: http://forum.xda-developers.com/showpost.php?p=28401190&postcount=2
and this seemed to work. the contact data seems to be the rpoblem? im really lost. but it works for now.
damnit. the phone worked for 1h after that i'm now where i started where nothing works. :/ anyone got a suggestion?

[Q] Grand rebooting problem help

my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.

crash, crash and crash again: please help me!

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

Camera keeps crashing after flashing factory image.

Had to unroot my phone recently, so I installed the latest factory image (9.0.0 (PQ2A.190405.003, Apr 2019)) without wiping data.
Seems to have mostly worked, however ever since my camera has been really flaky. Usually it just shows black screen and eventually crashes back to the home screen. Occasionally I can get it working briefly, but it tends to lock up shortly afterward. Anyone seen this? Should I just reflash? Maybe try an earlier image?
je55ter said:
Had to unroot my phone recently, so I installed the latest factory image (9.0.0 (PQ2A.190405.003, Apr 2019)) without wiping data.
Seems to have mostly worked, however ever since my camera has been really flaky. Usually it just shows black screen and eventually crashes back to the home screen. Occasionally I can get it working briefly, but it tends to lock up shortly afterward. Anyone seen this? Should I just reflash? Maybe try an earlier image?
Click to expand...
Click to collapse
a factory image flash without wiping data isn't an ideal scenario. Better to reflash after wiping the system/vendor/data without wiping the internal storage and see if it persists.
It shouldn't ideally.
SacredDeviL666 said:
a factory image flash without wiping data isn't an ideal scenario. Better to reflash after wiping the system/vendor/data without wiping the internal storage and see if it persists.
It shouldn't ideally.
Click to expand...
Click to collapse
While I could try wiping system/vendor partitions, I'd really rather not wipe data, as that's a whole lot of stuff I would need to start from scratch to set up (and without the ability to restore apps/data from Titanium Backup since I'm no longer rooted). If I was going back to stock from a custom ROM, then I could see it being necessary, but since I'm just going from an earlier (albeit rooted) stock image to a newer one, it doesn't seem like wiping data should be necessary.
je55ter said:
While I could try wiping system/vendor partitions, I'd really rather not wipe data, as that's a whole lot of stuff I would need to start from scratch to set up (and without the ability to restore apps/data from Titanium Backup since I'm no longer rooted). If I was going back to stock from a custom ROM, then I could see it being necessary, but since I'm just going from an earlier (albeit rooted) stock image to a newer one, it doesn't seem like wiping data should be necessary.
Click to expand...
Click to collapse
its about the data of the apps which you have is signed to a different operating system custom/signed so you get these force closure of apps when you try to use it over others.
you can use the same data if you are flashing another build of the same rom which isn't what you are doing. at the most what you can do is try clearing cache/storage of camera and see if it fixes if not the only way is to clean flash.
all the best :good:
Okay, so after trying several other variations of selectively wiping data and reflashing with no luck I finally took your advice and went for a full wipe and clean flash and... Camera is still crashing.
je55ter said:
Okay, so after trying several other variations of selectively wiping data and reflashing with no luck I finally took your advice and went for a full wipe and clean flash and... Camera is still crashing.
Click to expand...
Click to collapse
and you are on stock is what you are trying to say even with a clean flash right. no other gapps/manual installation of camera app done.
Could you share which version of rom build you are on and the build version of camera.
SacredDeviL666 said:
and you are on stock is what you are trying to say even with a clean flash right. no other gapps/manual installation of camera app done.
Click to expand...
Click to collapse
Flashed the latest crosshatch factory image using the flash-all.bat with the -w option to do a full wipe. Then immediately booted into the OS. Nothing else done with fastboot or adb.
Could you share which version of rom build you are on and the build version of camera.
Click to expand...
Click to collapse
Android version: 9
Android security patch level: April 5, 2019
Baseband version: g845-00009-181130-B-5157073
Kernel version: 4.9.124-g86541ee-ab5292322 #0 Fri Feb 8 01:27:08 UTC 2019
Build number: PQ2A.190405.003
Not sure how to look up the camera firmware build, but the camera app version is 6.2.024.239729896.
je55ter said:
Flashed the latest crosshatch factory image using the flash-all.bat with the -w option to do a full wipe. Then immediately booted into the OS. Nothing else done with fastboot or adb.
Android version: 9
Android security patch level: April 5, 2019
Baseband version: g845-00009-181130-B-5157073
Kernel version: 4.9.124-g86541ee-ab5292322 #0 Fri Feb 8 01:27:08 UTC 2019
Build number: PQ2A.190405.003
Not sure how to look up the camera firmware build, but the camera app version is 6.2.024.239729896.
Click to expand...
Click to collapse
yeah that would be the same version of cam build. could you also check the perms given for this app under app info.
SacredDeviL666 said:
yeah that would be the same version of cam build. could you also check the perms given for this app under app info.
Click to expand...
Click to collapse
Camera
Location
Microphone
Storage
je55ter said:
Camera
Location
Microphone
Storage
Click to expand...
Click to collapse
thats weird and find no reason it to crash randomly! with other camera apps is it the same or?
SacredDeviL666 said:
thats weird and find no reason it to crash randomly! with other camera apps is it the same or?
Click to expand...
Click to collapse
It's pretty much the same in all apps that use the camera. Sometimes it works, sometimes I just get a black screen.
Tried a clean flash from an older version (November), and while I didn't have time to test it exhaustively, I tried several times to open/close the camera and a few apps that used the camera, and I didn't get it to lock up or crash. Then I let the phone install updates, and now that its up to date again, I'm having the same camera issues again. So it seems like its something in one of the updates itself that's causing the problem, and not anything to do with how I flashed it.
je55ter said:
Tried a clean flash from an older version (November), and while I didn't have time to test it exhaustively, I tried several times to open/close the camera and a few apps that used the camera, and I didn't get it to lock up or crash. Then I let the phone install updates, and now that its up to date again, I'm having the same camera issues again. So it seems like its something in one of the updates itself that's causing the problem, and not anything to do with how I flashed it.
Click to expand...
Click to collapse
Exactly I experienced this on pie, Q non-issue, it's the latest camera update that breaks it
Great, so it sounds like I have to wait for the official release of Q to fix my camera.
je55ter said:
Great, so it sounds like I have to wait for the official release of Q to fix my camera.
Click to expand...
Click to collapse
...Aaaaand still not fixed on Android 10 after OTA update. Grrr....
je55ter said:
...Aaaaand still not fixed on Android 10 after OTA update. Grrr....
Click to expand...
Click to collapse
I think you have pretty much run out of road. Since you have already wiped your phone and reinstalled several times... and you can reproduce the issue immediately afterwards, I would say that is grounds enough for an RMA. Call Google and explain what you have done to date. They may have you wipe or reset again, but should ship you a replacement phone if it still crashes. Otherwise you'll just have to live with Pixel phone with no camera. You must be very patient... I know I would not have waited 6 months!

Android 10 - Factory reset needed?

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.

Categories

Resources