Sensor issues after installing and wiping "o" beta. - Nexus 5X Q&A, Help & Troubleshooting

So I installed the beta and decided to go back to 7.1.2.
I did a normal wipe in TWRP then reinstalled SAOSP.
The first problem I noticed was that the phone was slow to turn the screen on after pressing the power button or the fingerprint scanner.
The second problem was that the proximity sensor wasn't working in phone calls. I then checked a few others sensors and noticed that the rotation also want working.
I downloaded a sensor checking app and it showed that the proximity sensor had a value of 5 but it didn't change when covering the sensor.
First thought was a bad flash, so I re-wiped and installed a Nand backup that I knew was good. Same thing happened, so I tried PN. That didn't work.
Downloaded stock zip, backed up personal data, then did a complete wipe with the zip, internal data included. The problems stayed even on stock.
I have since read through whatever threads I could. This seems to be a random issue people have had in the past. Yet is particularly prevalent after the o beta.
Most people have suggested to just re-flash stock but that hasn't worked. The only suggestion I have read otherwise is to also lock and then unlock the bootloader in the process as well.
Who else has this problem and has anyone found a fix yet?

Ok, someone posted in another thread (PN) that the locking and unlocking the bootloader worked for them.
If you have the issue try it out.
Just remember to copy all your internal data to your PC or other storage to save it.

https://forum.xda-developers.com/showpost.php?p=72397601&postcount=10078
Link to solution

To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2

neth15 said:
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
Click to expand...
Click to collapse
I tried it this way but after flashing back to 7.1.2 stock, I now get a crash of com.android.phone immediately after booting, followed by a reboot.
Tried clearing cache but didn't help. Anyone know what to try to fix the crash?
UPDATE: Wiped data and now it's fine.

Related

Galaxy Note 10.1 SM-P600 Reboot Loop

Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!

Camera's dead, Jim

I did the developer preview for Nougat and everything was fine and dandy throughout the whole thing on my Nexus 5x. I got the official 7.0 release and now my camera won't open. If it does open it's black, freezes, and causes my phone to restart. I've already wiped after the update and started completely fresh and it's still not working. Has anyone else come across this issue?
Uhh nevermind, I got it working. For anyone else that comes across this issue, wipe the cache partition by booting into recovery. I also wiped my device again as well. Booted up and now the camera is working again.
majp89 said:
Uhh nevermind, I got it working. For anyone else that comes across this issue, wipe the cache partition by booting into recovery. I also wiped my device again as well. Booted up and now the camera is working again.
Click to expand...
Click to collapse
If you are unlocked, which I recommend if only for troubleshooting purposes, try reflashing the vendor.img and boot.img if this arises again.

OnePlus 3 - Android Oreo Camera Unknown Error!

Hi,
Today im facing a strange issue with camera
Actually all the applications related to camera are not working
It seems there is a problem in the physical camera it self !
Snapchat, instgram once i open its cam, original camera, and google camera..
It shows me this message
"Unknown Error"
My phone is already updated to stable version 5.0 which is oreo.
By the way, I already restart my phone, and also clear the data & cach of the camera : it doesn't work
Just to be safe, have you tried other ROM? If that still doesn't work, then try downgrading to Oreo. If all fails, then welp, at least you know that ROM isn't the cause of it.
dream2poet said:
By the way, I already restart my phone, and also clear the data & cach of the camera : it doesn't work
Click to expand...
Click to collapse
same happened with me on open beta 27.
i clean flashed ob 28, everything good so far.
try a factory reset or a clean flash.
I've had this issue before where I flashed nougat modem onto marshmallow and it gave me this error..it took accidentally wiping my phone to figure this out.
So try reflashing 5.0 rom or check whatever zip you flashed is not the culprit.
F4uzan said:
Just to be safe, have you tried other ROM? If that still doesn't work, then try downgrading to Oreo. If all fails, then welp, at least you know that ROM isn't the cause of it.
Click to expand...
Click to collapse
LELBOT said:
same happened with me on open beta 27.
i clean flashed ob 28, everything good so far.
try a factory reset or a clean flash.
Click to expand...
Click to collapse
tofuboi01 said:
I've had this issue before where I flashed nougat modem onto marshmallow and it gave me this error..it took accidentally wiping my phone to figure this out.
So try reflashing 5.0 rom or check whatever zip you flashed is not the culprit.
Click to expand...
Click to collapse
Thank you guys for helping me,,
I did Factory Reset (without internal storage) and all working fine now..
I think the problem happen because I did not do factory reset once i updated to Oreo

Oneplus 5T bootloop

Hi there,
Yesterday I rooted my oneplus 5T and installed TWRP 3.2.1 & masgisk. Then, I´ve installed Pixel experience AOSP which seemed like fairly stable from the description. Everything went fine, the OS started I started configuring it then after setting the password I got the OS having always the setting app to crash. So, I thought well, I can just go to recovery and try once again factory reset. Otherwise, I can mount the recovery and install another ROM. I went to recovery and to my surprise it was asking for a password and mine didn´t work. I tried the factory reset and still the encryption stayed. I found that this version has a decryption problem and all my files were encrypted and not accessible, that was fine, since I had everything backed up. So, I have installed the new version of TWRP which seems to fix this issue after loosing all encrypted file. I have formated the data, system, dalvic and cache and installed once again pixel exerience but the OS keeps on bootloop. Have anybody seen something like this? How should I fix it? My best guess was to reinstall stock OS via adb, but in the past I've rooted a couple of devices and I've never seen something like this.
Thanks in advance

Oneplus One Bacon New Bootloop!?

Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
AnotherStupidUser said:
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
Click to expand...
Click to collapse
You already lost apps by wiping data, but you still have your photos.
If you had GApps installed before android version upgrade, you now need to flash android 11 GApps. Wiki.lineageos.org tells you what and how.
Thank you for your help. Surprisingly for some reason I found a work around as the unofficial GApps didn't work as well. I wiped data again, so the apps were gone (it took me 3 hours to restore that), but all files were still there and I flashed back to 17.1 with GApps and it worked. Phone is working same way as before. Guess I will wait a LOOOOOOOONG time now until I will try 18.1 again. But again thank you

Categories

Resources