Hi,
i flashed my Pro and unfortunately wiped the persist partition. After booting everything worked fine except the proximity sensor. I searched the internet and found a solution to flash the persist_1.img. After flashing the persist_1.img the Pro crashed again and again with the blue LED on. The only way to use it was wiping the persist partition and reinstalling, but now i have no proximity sensor.
Is there any solution to get my proximity sensor back?
Thanks!
Edit: Unfortunately i am not allowed to post links...
Solved. I flashed 1.9 with qfil and after that installed aicp.
Thats the short Version, it took me 5 hours at least...
Related
The situation is this, i try to change my phone to efs partition, i changed and after some weeks i decided get back to ext4, but during this procedure, the partitiol table got corrupted/broken, so everytime i flashed a rom it was good but on recovery, the data partition shows an error on log, when it booted, i noticed that my sensors stopped working, rotation screen brightness controller, among others, i had no other option than restore to stock, and i did, but my sensors keep not working, and i already flash the 5.0 and 6.0.1 and the result is the same, isnt suppost a rom include the sensor drivers?
Im 100% sure it isnt a hardware problem, please if anyone could help me i would be very gratefull, thanks
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.
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, recently i had a problem & faced bootloop that's why i flash a fastboot rom & then again flashed the latest version of the custom rom i was using. After few hours i noticed that none of my sensors were working, although i have fixed this sensor problem now by flashing the persist.img file from fastboot rom but still selfie camera problem is there.
I tried controlling is manually using an app it's working perfectly then but generally at the time of video calling or switching to front cam it's not even working for once.. please help me how to fix this problem!!
Solved!!!!
learnerz said:
Hi, recently i had a problem & faced bootloop that's why i flash a fastboot rom & then again flashed the latest version of the custom rom i was using. After few hours i noticed that none of my sensors were working, although i have fixed this sensor problem now by flashing the persist.img file from fastboot rom but still selfie camera problem is there.
I tried controlling is manually using an app it's working perfectly then but generally at the time of video calling or switching to front cam it's not even working for once.. please help me how to fix this problem!!
Click to expand...
Click to collapse
Is it solved??
ILoveAndroidCustomization said:
Is it solved??
Click to expand...
Click to collapse
yes
How did you fixed it? I still have the same issue