Help! all my sensors stopped working, i need a copy of the persist partiton! - Google Pixel 3a XL Questions & Answers

so all my sensors stopped working when I upgraded to android 10, could someone with root help me with a copy of the persist partition? it seems im having the same bug that other users are having with the older pixel 3 XL

Have you tried to factory reset and see if they all come back??

I had same issue on my píxel 3a. I read a lot about it, maybe corrupt partition etc... Finally I did a simple Job. Download stock image of Pie from Google repo, open bootloader and flash vía Fastboot. Then Phone automatically update to 10. Every sensor works again. But be carefull. This is an issue with Bluetooth connections.... So as soon as I pared my headphones sensors stopped working again. So I flashed again Pie and now I have 10 with working sensors But no Bluetooth connections

Related

[Q] Sensors not working after update

Hi
This is my first post here. I have come across a problem and need some help. We bought 4 galaxy grand i9082s in Pakistan and I flashed Indian XXUBMI1 4.2.2 firmwares on all of them using odin 3.07 (since 4.2.2 updates for Pakistani firmware were not available so I chose the neighbor's ). The updated firmware works fine on all of the devices except one whose motion sensors (accelerometer, gyro and orientation) are no longer working. The Samsung test feature (*#0*#) showed that accelerometer and gyro were not picking any data at all (x=0, y=0, z=0, and it remains zero). I then reinstalled the old firmware 4.1.1 and the sensors were working fine with it, but again after upgrading to 4.2.2 they stopped working (virtually making the phone not-upgradable to 4.2.2). I tried different countries' firmware on the phone but the result was sensors are working in 4.1.1 but not 4.2.2. Please guide me how to solve this problem and make the phone at par with the others.
P.S. Only one device has encountered this problem
I have tried the following for a solution:
1. Factory reset and data wipe
2. Downgrade to 4.1.1 (sensors working fine) and re-flash 4.2.2 (sensors no longer working)
3. Downgrade to 4.1.1 (russian version, sensors working fine) and get the OTA 4.2.2 update (sensors no longer working)
4. Installed philz_touch_5.15.0-i9082 recovery, rooted the phone with Update-SuperSU-v1.25 (however I don't know of any software that could reset the sensors)
5. Tried installing different kernels
6. Calibrate with Sensor Tester (works only in 4.1.1 but doesn't do anything on 4.2.2)
My guess is the problem is with the bootloader (or where ever the drivers are), maybe I made some mistake during the first upgrade and it set some flag to dirty or something, now its not resetting (because the update is working fine on rest of the 3 devices, if there was any hardware compatibility issue it wouldn't be working on them too)
Now I even tried NAND reset all on odin but no luck :crying:. Same problem persists (works in 4.1.1 but not in 4.2.2) and I am scared to use any other options in odin. I also just tried rooting the phone and checking options in wanam xposed software but nothing could be found. Also tried cleaning delvik cache and formatting everything from recovery such that the phone only showed galaxy grand sign and not move any further, then I flashed the firmware (latest vietnamese one XXUBMJ4), but same problem :crying:.
I don't think this is because of some wrong settings (because the test mode should pick something no matter what the settings, right). And since it works in 4.1.1 means hardware is also fine. Then what the heck is wrong with this particular phone. I noticed that on other phones (the ones on which everything is fine with 4.2.2), I noticed that RF cal and HW Rev show unknows while on this one they show 20121109 and REV0.4 respectively. Does that make a difference???
Please help, I haven't been able to sleep since 2 nights now because of this

Gyroscope and other sensors not working after recent updates. HELP!

Thank you for clicking on the thread.
I've loved my Zenfone 2 for a while now. I have the 64gb 1080p model. It was a well priced powerful phone for what I wanted.
However, I recently received an asus software update that completely borked the Gyroscope and some other sensors. I have read about similar issues online and testing the sensors reveals that they're not working.
Does anyone know how I can fix this? I have been unsuccessful in trying to install CyanogenMod13 or even TWRP/CWM. I rooted my phone and the bootloader is unlocked (white backscreen upon loading).
It seems as though ASUS doesn't want to fix this, would upgrading to a custom ROM provide firmware that would properly recognize and use the gyroscope as input?
I've tried wiping the system cache in the stock recovery, resetting to factory new and everything to no avail.
I am willing to "tip" or "pay" for someone's time if they can help me as I cannot auto-rotate or use any applications requiring certain sensors.
Thanks for your time.
I've upgraded to CM13 successfully now and the gyroscope is still not even recognized in Sensor applications. Is it hardware?
solution?

Sensor issues after installing and wiping "o" beta.

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.

Auto rotate doesn't work

Hi All, my redmi 5a auto rotate doesn't work, I don't know why but I've experienced a tragedy that maybe connected with this problem.
I use AOSP Extended ROM for Rolex in my Redmi 5A Device, as long as I use it I don't have any problem, but yesterday I've tried to restore my kernel into this ROM Stock Kernel ( I Use Direwolf Unified Before, Many Times I Try Other Kernel Also But And Never Had Such A Tragedy) After I Restored the original kernel, then I wipe my dalvik and cache as usual, BUT, Suddenly The Boot animation Stucked before it show's the AEX Logo, So I Think It Was A Bootloop Simple Problem, Than I Reinstalled My AOSP Extended OS, Than Something Happened, Even Since The First Boot It's Stucked At The Same Point, Than I Tried To Re-flash it again, and after that it still like that, so I was thinking that my External Memory Data Was Corrupted, So I Tried To Copy The File Directly From My PC To My USB OTG (I copied same AOSP ROM) than I reflash it but it still like before, than i start thinking if this ROM file (in my PC and SD card) is corrupted, so I tried to install PE ROM, But The Result Is Still Same As Before, Stucked At Boot Animation Than Forced Shutdown.
Well after that I think my device is get a serious problem such as hard brick or soft brick, than I tried to do clean flash to MIUI 10 Fastboot ROM With My PC, BUT the time elapsed is more long than usually (About 20 minute) waiting for booting and finally my device is normal, so I immediately install TWRP Custom Recovery (3.2.3-1 by FenFern) And Installing AOSP ROM Again (I Swear I Love This ROM) Everything seems normal no problem, restoring app, rooting, personalization, and etc.
Well the problem with auto rotate is coming when I see some funny videos on YouTube, my devices ONLY CAN ROTATE TO THE LEFT, AND CAN'T ROTATE AUTOMATICALLY AND CAN'T ROTATE TO THE RIGHT SIDE, I tried many game's app and watching some anime's in video player, Even If I Switch to auto rotate mode.
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
SandipS said:
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
Click to expand...
Click to collapse
Well yeah it's working, except the auto rotate

CrDroid broke(?) my NFC on Redmi Note 8t

Hi.
I have been using CrDroid custom ROM for a few months. Yesterday I decied to switch to xiaomi.eu MIUI 12. Installation went smooth and everything seemed fine until I tried to turn NFC on through the quick menu. I clicked the button and it turned blue, but NFC icon didn't appear in the status bar. I then tried to turn it off, but clicking the button did nothing, it stayed blue. I couldn't change any NFC related settings in settings, they were all grayed out. I then decided to flash xiaomi.eu MIUI11, which worked ok for me when I tested it a few months ago, now NFC doesn't work there too. Same issue. I tried to flash stock MIUI11 through MiFlashTool, but NFC doesn't work there too! I went back to crDroid and NFC works there, so the issue isn't hardware related. I also tried Paranoid Android, but the NFC is now broken there too (it used to work)! Does anyone have an idea on how to fix NFC? I don't know what crDriod did, but it seems it screwed something up big time. I really need NFC in my phone. Any help would be appeiciated! Thanks.
Behenate said:
Hi.
I have been using CrDroid custom ROM for a few months. Yesterday I decied to switch to xiaomi.eu MIUI 12. Installation went smooth and everything seemed fine until I tried to turn NFC on through the quick menu. I clicked the button and it turned blue, but NFC icon didn't appear in the status bar. I then tried to turn it off, but clicking the button did nothing, it stayed blue. I couldn't change any NFC related settings in settings, they were all grayed out. I then decided to flash xiaomi.eu MIUI11, which worked ok for me when I tested it a few months ago, now NFC doesn't work there too. Same issue. I tried to flash stock MIUI11 through MiFlashTool, but NFC doesn't work there too! I went back to crDroid and NFC works there, so the issue isn't hardware related. I also tried Paranoid Android, but the NFC is now broken there too (it used to work)! Does anyone have an idea on how to fix NFC? I don't know what crDriod did, but it seems it screwed something up big time. I really need NFC in my phone. Any help would be appeiciated! Thanks.
Click to expand...
Click to collapse
it's very strange thing, normally clean flashing through fastboot mode fixed every issues,
are you sure you flashed firmware for 8t not for 8
Redmi 4A abdal said:
it's very strange thing, normally clean flashing through fastboot mode fixed every issues,
are you sure you flashed firmware for 8t not for 8
Click to expand...
Click to collapse
Yes i'm sure I flashed willow version. I was suprised when flashing through fastboot didn't fix it too!
Ok I fixed it! You can find the full thread on xiaomi.eu forum if you search for "NFC doesn't work on MIUI, Redmi note 8t" but basically:
-Wipe everything except USB, SDCard
-Format Data
-Reboot Recovery
-Flash PA4 - can't switch NFC in the OS
-Reboot into TWRP, flash the NFC fix zip and MIUI11 (NOT MIUI12) firmware (I'm not sure which one actually fixed NFC)
-Reboot into PA4 - now NFC works
-Dirty Flash MIUI.eu 12 over PA4
-Format Data
-NFC can be now switched, when I touch the back of the phone with my card it does the "Can't recognize NFC" sound so it definitely works!
-Now you could probably do a clean flash and still have the NFC working, but everything seems fine after the dirty flash so I see no reason not to do it unless you start getting battery drain issues or something.
NFC fix file:
https://forum.xda-developers.com/attachment.php?attachmentid=5118065&d=1602959568
Behenate said:
Hi.
I have been using CrDroid custom ROM for a few months. Yesterday I decied to switch to xiaomi.eu MIUI 12. Installation went smooth and everything seemed fine until I tried to turn NFC on through the quick menu. I clicked the button and it turned blue, but NFC icon didn't appear in the status bar. I then tried to turn it off, but clicking the button did nothing, it stayed blue. I couldn't change any NFC related settings in settings, they were all grayed out. I then decided to flash xiaomi.eu MIUI11, which worked ok for me when I tested it a few months ago, now NFC doesn't work there too. Same issue. I tried to flash stock MIUI11 through MiFlashTool, but NFC doesn't work there too! I went back to crDroid and NFC works there, so the issue isn't hardware related. I also tried Paranoid Android, but the NFC is now broken there too (it used to work)! Does anyone have an idea on how to fix NFC? I don't know what crDriod did, but it seems it screwed something up big time. I really need NFC in my phone. Any help would be appeiciated! Thanks.
Click to expand...
Click to collapse
i think flashing the latest vendor will fix it, but since you did then good
I followed your guide, but unformately, not working nfc.
I have my own vendor backup from miui11 and not working also
I tried miui11 then miui12 firmware.
Edit:
Big thank You
My nfc started working in miui. It is something with firmware but I also flashed nfc fix.

Categories

Resources