Hey everyone,
My accelerometer and gyroscope direction are wrong. When I turn on automatic rotation in Android it goes to landscape when I hold my phone in portrait mode and vice versa.
The problems started after I used the Xiaomi Flash Tool to return to stock. I used the clean all and lock option. I used TWRP to flash persist.img to get rid of the device search error in MIUI. After this my accelerometer started to be 90 degrees inverted.
The problem is fixed by flashing the persist.img (if you didn't make a backup of your persist partition) from the Telegram group for the Mi Mix 3 5G: https://t.me/mimix3_5G
I've got same problem with my phone.
Can you provide instruction how to fix it ?
Related
Model : Yureka A5510 [not plus]
my phone was working perfectly .. no issues at all.. after JIO 4g launch. I read some of the articles to enable VoLTE without using JIOVoice application. I though to enable VoLTE.. and tried to install a firmware for my Yureka A5510.
and I hardbricked my phone. Just redlight blink on top left cornor. NO BOOT, NO FASTBOOT, NO RECOVERY
I googled. and found some article to unbrick by flashing eMMC image on SD card to bring it in to fastboot mode. (using six pins on the motherboard and key comnbination)
finally I am succeed to flash the STOCK firmware by FASTBOOT.
But I lost the IMEI, so NO network.. again googled a lot and I made the IMEI fix with the help of QXDM Tool.
now the problem is with the touch screen. it works fine after a restart untill I press the Lock / unlock button.
After Unlock the touch pointer shows on different locatoin and lower 1/4 part doesn't respond.
I enabled developer mode and enable show touch points... that tells me the location of the touch.
I AM PRETTY MUCH SURE IT IS NOT A HARDWARE ISSUE, BECAUSE IF WORKS FINE IN RECOVERY MODE(CWM RECOVERY) AND ONCE AFTER EVERY RESTART.
.. CAN YOU HELP ME .. PLEASE.
PLEASE TAKE SOME TIME AND READ IT.
I have same Yureka model YU5510A and i soft bricked my phone when i was flashing VoLte Rom. It's been 1 whole month and i haven't found any solution. i tried flashing through CM recovery and fastboot and YGDP tool but non of it works. I am so pissed off. Did you find any solution bro?
So I was running LineageOS 18.1 without problem before. Today I wanted to switch to another ROM, so I followed the tutorial and tried to flash back to 11 based OOS. Since there is no TWRP for 11, I used the 9008 package to flash it back to OOS 11.0.4.4. After flashing, the phone boots, but fingerprint sensor breaks. I unlocked and restored my persist.img and it does not work still. I was in panic and tried to follow the tutorial to downgrade to OOS 10.5.4, and this is where the nightmare begins. After flashing, the system does not boot anymore, the only thing I can see is a screen like below:
QUALCOMM CrashDump Mode
err_qdi.c:1038:EF:sensor_process:0x1:SNS_REG_INIT:0x5c:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - sl
pi crashed.
subsys_unregister
Click to expand...
Click to collapse
9008 also does not work anymore. Flashing anything will result in the same CrashDump screen. Since after 9008 the bootloader will be locked and unlocking requires to enter the OS and enable OEM unlock, I am not able to use fastboot to flash partitions. I think I am pretty stuck. Anyone know if I can do anything to recover, or I need to send it to the service center for a motherboard exchange? Thanks.
Try MSM Download Tool. It restores your phone back to factory state.
Guyinlaca said:
Try MSM Download Tool. It restores your phone back to factory state.
Click to expand...
Click to collapse
I already tried that and seems like it's that which corrupted my persist partition. I sent it to OnePlus service center and they also cannot help me and suggest me to change the motherboard (~2400CNY). I have the backup of my persist partition but flashing it back does nothing.
UPDATE: I sent the phone to service center. They don't have much luck except flashed OOS 11 to make it bootable, and suggested me to swap the motherboard or phone itself. I tried flashing various OOS and HOS images, but non seems recover my persist partition even if I flash my backup. Currently:
Non of the sensors is working in *#808# (including fingerprint which is the most obvious)
WiFi is not working (won't turn on at all)
Rear main camera will shake like crazy when activated
I think in this stage I'm pretty ****ed up. Me and service center also tried flashing back to OOS 10 instead of 11, but cannot get it booting at all (black screen only). All of this seems pointing to me flashing with MSMDownloadTool on a perfectly fine third party ROM. Just don't do that and use fastboot to go back to stock OOS.
One day my proximity sensor randomly stopped working, I fixed it once using the incoming calls dialer method but then it stopped again. After that my light sensor stopped working. I thought it was my persist partition that was corrupted but I tried flashing the fastboot from and even tried flashing the persist IMG extracted from the fastboot rom but it didn't fix it. I don't know if the hardware itself is broken or if it is a software issue. All my other sensors work. Someone, please help me fix it. I can't go to the service centre to repair it as it was purchased in India and now I'm in the UK
Hi everyone,
I have the all classic fingerprint sensor not working after display got changed problem and even an MDM tool flash / EDL mode did not fix it.
If I calibrate it from the debug menu it works until the next restart
Does anyone have the corresponding and in an OK state persist.img? (I have the European version)
Thank you!
side info:
To calibrate it I type in the dialer: "*#899#", then "After Sales Calibration" and 6776.
Hello guys, I have a problem with my Oneplus 8 Pro IN2023. the proximity sensor, light sensor, screen rotation etc. do not work. I have tried to install different versions of oxygenOS and each has the same problem. when trying to return to android 10, a crashdump appears, which prevents it from starting. from the information i found there may be a problem with the persist.img folder. could someone please help me with this problem and share the file or suggest another solution?