Hi there,
I suspect this error arises when having used an app concerning navigation beforehand.
Afterwards, not always, but most often all sensors are failing completely. Until rebooting the Redmi.
I applied the persist.img fix via EDL by the MiFlashTool. However, didn't fix the issue.
As far as I understand this fixes just those never working sensors anyway.
Any idea? BTW, this issue has haunted my during the use of several custom roms.
I'll be using Miui the next days to check if the bug is there too.
Related
It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.
Hello guys! After experiencing all custom ROMS including Xiaomi.EU, figured out that every single one has some small inconvenience for me and planning to return to stock, eventually using only Magisk and potentially a custom Kernel.
Managed to install every single version of Global Developer ROM, everything works well except the FaceUnlock that was gone, (the phone remained stucked in China region) and I am not able to access the fingerprint section, after few tries it brings me an error message.
Tried also using MIFlash , but the Fastboot ROM writting took 3 sec to write and stopped as successfully, then nothing but bootlooping.
Currently is the phone is functional, but as mentioned before not able to setup new fingerprints (using cache and data from old recovery and those work) neither Face Unlock.
Tried to Google any kind of solution, but unfortunately nothing worked.
Any suggestion is appreciated.
I see that nobody is interested to support, so I continuously researched and figured out that doing a full wipe and following these steps from this post will solve my problem:
https://forum.xda-developers.com/mi-8/help/chinese-mi8-to-global-instructions-t3839665
From I don't know which reason I was blocked on China region without the possibility to changing it.
Hello guys, I need your help. I discovered that on xiaomi.eu rom compass is behaving kinda wrong. I discussed about it here but I didn't get any solutions for that problem. On Global Stable ROM everything is fine, compass stands still but on the xiaomi.eu it keeps increasing value when the phone is laying on the table. I discovered also that in the diagnostic menu the value of Z axis is increasing (screenshot). As it's not a hardware problem it must be something wrong with the software. Can you help me to solve this problem? If I should check anything else or give you more feedback about it, just tell me. BTW I tried factory reset twice, even flashed back Global rom and then again xiaomi.eu. Also I cleared the compass data and tried to calibrate it many times. I hope it's not a Chinese rom problem on which xiaomi.eu is based on
Seems like the latest update (9.10.31) finally fixed that issue. The thread can be closed/deleted
Hello devs,
My 3t's Proximity and Ambient Sensor both sensor stopped working after I updated from rooted 9.0.5 to MSM Android 10.
After that, I've tried everything but they are not getting back to work. Prior flashing 10, both were working fine.
So far I tried.
1. Flashed official 9.0.5 rom
2. Flashed official 8.0 rom
3. Factory reset on both rooms.
4. Stable modem & firmware files.
5. Flashed "Fix all sensors" file.
6. Tried *#808# can't seems to be showing any data or presence of sensors.
Any suggestions, will be highly appreciated
I had problems with sensors (accidently deleted sensors dir from persist partition, it contains sensors calibration, wifi and bt hw address).
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.
ppajdek said:
I had problems with sensors (accidently deleted sensors dir from persist partition, it contains sensors calibration, wifi and bt hw address).
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.
Click to expand...
Click to collapse
Still my Proximity, Ambient and MSensor isn't working.
ppajdek said:
I had problems with sensors (accidently deleted sensors dir from persist partition, it contains sensors calibration, wifi and bt hw address).
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.
Click to expand...
Click to collapse
Would flashing any oneplus 3t pulled persist.img solve my problem?
hasanin.xaidi said:
Would flashing any oneplus 3t pulled persist.img solve my problem?
Click to expand...
Click to collapse
Persist partition contains wifi and bt hardware address, so if you flash persist.img from another op3t you would end up with the same wifi and bt address.
You would need to backup your persist partition, then backup wlan_mac.bin and /bluetooth/.bt_nv.bin, flash another persist.img and restore the two files.
Then check is your issues are solved.
Hi
Is there a way to install gps drivers again (i have some twrp backup I think)? I was on pie custom rom. I passed the mobile to my mother. She realized sth is wrong with gps. Moto has problem with fixing gps signal. I backed to stock to check if it helpes, but the problem persist. Any ideas?