Develop Bugs

[Q] My M8 turned sucks after lollipop update..

I rooted my m8 on stock android 4.4.4 and since the lollipop update rolled out, I applied my backup from TWRP and flashed stock recovery then relocked bootloader. Installed Lollipop via OTA, unlock bootloader and flashed TWRP then flashed supersu. So I'm on android lollipop 5.0 and rooted. I don't know what went wrong, my phone seem too laggy ( mostly when I'm trying to type on facebook messenger, every times i type a text it stacks for some times) And most importantly, some stocks application such us HTC sense TV and Scribble not working anymore. every time I open, it say " stopped unexpectedly ". I don't really know what I might do to get it fix, please advice me.

I have the same problem, basically. I have an unrooted, completely stock phone that got updated through OTA. Ever since the update the phone is lagging, the battery life is visibly worse, and the only visible change is the color of the quick settings and the appearance of notifications. Lots of people are excited and eager to update to Lollipop, but based on my experience I really regret updating. I wish there was an easy way to revert to 4.4.4, but unfortunately it takes too much time which I don't have at the moment. So I decided to wait till May, when Sense 7 is supposed to arrive to M8.
Many of the initial problems with Lollipop were solved by factory reset, but certainly not all. It remains to be lagging and frustrating. At least it's free. But on the other hand, if I bought it, I would certainly return it and ckaimed a refund. As it is, I just have to suffer through it.

unifex_ said:
I have the same problem, basically. I have an unrooted, completely stock phone that got updated through OTA. Ever since the update the phone is lagging, the battery life is visibly worse, and the only visible change is the color of the quick settings and the appearance of notifications. Lots of people are excited and eager to update to Lollipop, but based on my experience I really regret updating. I wish there was an easy way to revert to 4.4.4, but unfortunately it takes too much time which I don't have at the moment. So I decided to wait till May, when Sense 7 is supposed to arrive to M8.
Many of the initial problems with Lollipop were solved by factory reset, but certainly not all. It remains to be lagging and frustrating. At least it's free. But on the other hand, if I bought it, I would certainly return it and ckaimed a refund. As it is, I just have to suffer through it.
Click to expand...
Click to collapse
ႈI guess, there only way to switch back to stock totally is to s-off but I am not sure if we can still apply nondroid back up of 4.4 stocks might work on lollipop loaded device. its so annoying ^_^

Facebook and Facebook Messenger simply have issues. The big problem is that when sounds are enabled in those apps they lag terribly running ART. ART is probably the reason why you're having issues with other apps, which would be remedied by a factory reset and reinstalling all the apps. I don't see any reason why you'd need to be s-off to flash back to a nandroid backup of 4.4. The only possible issue I could imagine you having would be compatibility issues with firmware, and I think that would require you to be s-off to revert back to, but I think 4.4.4 should work with 5.0 firmware. Can't say for certain though since I'm on Verizon and I'm not sure what carrier you're on, but I'm running 5.0.1 on 4.4.4 firmware. I've run several Sense 6 5.0.1 ROMs and they have been just as fast and even more battery efficient than 4.4.4.

You could always flash a Kit-Kat ROM while you wait for Google to address those bugs with the next release. You don't have to S-Off to go back to the older firmware if you don't want to.
If you want to stay stockish, I recommend Maximus HD.

My phone is turning worst and worst, now i can't even screenshot due to luck of storage it says. So I don't have to s-off to roll back ? All these issues are due to Android L or could it be becoz of me, I flash old TWRP ( 2.7). One more things, I do I flashed my local font on HTC ? I use all fontchangers and I even flash it via fastboot but it doesn't seem overwrite. I can't install busybox too.

minkutha said:
My phone is turning worst and worst, now i can't even screenshot due to luck of storage it says. So I don't have to s-off to roll back ? All these issues are due to Android L or could it be becoz of me, I flash old TWRP ( 2.7). One more things, I do I flashed my local font on HTC ? I use all fontchangers and I even flash it via fastboot but it doesn't seem overwrite. I can't install busybox too.
Click to expand...
Click to collapse
Most of your issues are not Android L related but more on user side. Make a backup of your current ROM on ext_sd, make a backup of your internal storage to ext_sd or PC.
Change your TWRP version to 2.8.5.0
In TWRP select WIPE then FORMAT DATA - yes
Reboot recovery
Restore your backup

ckpv5 said:
Most of your issues are not Android L related but more on user side. Make a backup of your current ROM on ext_sd, make a backup of your internal storage to ext_sd or PC.
Change your TWRP version to 2.8.5.0
In TWRP select WIPE then FORMAT DATA - yes
Reboot recovery
Restore your backup
Click to expand...
Click to collapse
I can't download 2.8.5 it aint moving after 99% :S

minkutha said:
I can't download 2.8.5 it aint moving after 99% :S
Click to expand...
Click to collapse
How ? Have you managed that ?

for me on lollipop on the m8. lot of features did not seem to work. like the nfc, screen rotation, g sensor, flashlight, and proximity sensor. so i tried to goto a custom rom and it still didnt work. anyone else have this problem?

For lag removing, disable Nu player in developper options.
As per the rest.. my M8 kicks ass using completely stock lollipop 5.0.1
No lags, no FCs, no misbehaving.
Sent from my HTC One using XDA Free mobile app

No issues here since I jumped to Lollipop. Then again, I'm technically not stock. I'm on Viper Rom.

ckpv5 said:
Most of your issues are not Android L related but more on user side. Make a backup of your current ROM on ext_sd, make a backup of your internal storage to ext_sd or PC.
Change your TWRP version to 2.8.5.0
In TWRP select WIPE then FORMAT DATA - yes
Reboot recovery
Restore your backup
Click to expand...
Click to collapse
I tried that and it still lagging on keyboard then I flashed Revolution HD and same issue. Lately, I found out that comes from Fb messenger, I keep in app sound alerts off and now my keyboard is flawless. I'll just wait for 5.0.2 to go back to stock.
ckpv5 said:
How ? Have you managed that ?
Click to expand...
Click to collapse
Yes bro, I updated it from TWRP Manager.

anjesh12 said:
for me on lollipop on the m8. lot of features did not seem to work. like the nfc, screen rotation, g sensor, flashlight, and proximity sensor. so i tried to goto a custom rom and it still didnt work. anyone else have this problem?
Click to expand...
Click to collapse
For me, its all becoz of TWRP 2.7. TWRP 2.8.5 going smooth on lolipop M8.

TWRP: failed to mount \data, \system, \cache

Hey all,
Fairly new to custom roms, so hopefully I'm asking a legit question. My phone is a D855, currently on DU 10.3. I wanted to upgrade to the 10.4, doing a clean install, but I seemingly cannot wipe anything. TWRP (using 3.0.2) will give an error message: failed to mount \[...]. Interestingly, flashify labels the recovery as Stock, so maybe there is a connection.
I have been doing some googling/"xda-ing" and as it seems, going back to stock can help. BUT, for one, I hope that there's an easier way, and also I would like to know what's causing this issue. Maybe it can be avoided somehow? So maybe someone can help me with that?
Cheers.

Just going to add a few more specific questions. As I am rather unexperienced, I don't want just to try things out without a confirmation that it's safe to go:
- TWRP: can I just try and reflash the newest one via flashify? Or maybe recover an old backup and update? Might it solve the issue and is it safe to go?
- If I have to revert back to stock: I'm coming from stock MM -> root -> Dirty Unicorns. Can I revert back to MM directly using that LG up method, or would you rather recommend flashing Lollipop, if I want to root again anyways? There seems to be a plethora of options for flashing stock (MM to MM, MM to LP, LP to MM, ...) and I am not sure which one applies here...

Hey. I had similar problem with my ls990. And tried all means to fix. Twrp was not mounting the system and sometimes internal storage appears as 0mb. It was so frustrating. So i resorted back to stock. But why flashing stock i got hooked at 98% and since then i was not able to do anything. My phone hardbricked.

Ugh, great prospects. :\
Really hope I can sort this out. At least, my phone is running fine so far, so no need to hurry. Glad for any idea!

Dellocatus said:
Ugh, great prospects. :\
Really hope I can sort this out. At least, my phone is running fine so far, so no need to hurry. Glad for any idea!
Click to expand...
Click to collapse
Wait. Let me understand you well. U can boot up phone? U mean the only issue is you not able to flash anything via recovery right?

Oh, forgot to mention explicitly that the phone is still running fine. So yeah - I just cannot wipe and thus cannot flash anything. So for now, I am stuck with the rom I am on, unless I find a solution to the problem.

Flashing back to stock

Hello, I am currently on PureNexus Rom with twrp 3.0.2RC1 on the pixel xl. I would like to flash back to completely stock because I am having some issues. I found a step by step tutorial but am apprehensive because some steps confuse me. I already got into trouble once when trying to flash PN rom. I don't want to do anything stupid like use a wrong file or anything like that. Is there anyone that could assist me if I run into issues. Also, I have just created a backup but if I flash to stock and run into trouble, I wouldn't be able to restore my backup, would i?? I would think flashing stock removes twrp Which I would need to restore a backup and think i would have a vendor image issue, right?
Any input is greatly appreciated.

What issues do you have?
Maybe no need to flash stock.
I myself flash back to stock every 6 month just to clean things up even it is not necessary.
I pm you my infos
Stock
Dl titanium backup all your apps
Backup that folder to pc
Backup everything else you need back to pc
You need latest Google drivers for flashing stock.

Check out unified Android toolkit helps me get back to stock very easily

mikaole said:
What issues do you have?
Maybe no need to flash stock.
I myself flash back to stock every 6 month just to clean things up even it is not necessary.
I pm you my infos
Stock
Dl titanium backup all your apps
Backup that folder to pc
Backup everything else you need back to pc
You need latest Google drivers for flashing stock.
Click to expand...
Click to collapse
Thanks for the replies. I was having a issue with battery drain. My text messages, if not looked at, would repeatedly wake up the screen every minute. In the course of about 5 hours, Android operating system would chew through 38% battery. I did a factory reset and reinstalled PN and the issue appears to be corrected. Don't know what was causing it, tried to isolate the issue but could not find. So, for now, i will stay on this rom as long as the issue doesn't reappear. I think somehow ambient display was messed up even though it was off.
Sent from my Pixel XL using Tapatalk

Ok if the issue comes back maybe you can try a different rom.

[bricked device] OP3 shows yellow screen

Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.

Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/

Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post

Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on

Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.

tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.

I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.

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!