Hi i have PixelUI_13.0 rom on my redmi note 8t, i have a problem, the accellerometer, orientation, temperature, gyroscope sensors doesn't work.
I've tryed to flash persist.img from the stock rom (willow_global_image_V12.5.6.0) but the problem is not solved.
Any help?
P.S: please don't tell me i need to reflash stock rom and the custom another one time.
Luigi2201 said:
Hi i have PixelUI_13.0 rom on my redmi note 8t, i have a problem, the accellerometer, orientation, temperature, gyroscope sensors doesn't work.
I've tryed to flash persist.img from the stock rom (willow_global_image_V12.5.6.0) but the problem is not solved.
Any help?
P.S: please don't tell me i need to reflash stock rom and the custom another one time.
Click to expand...
Click to collapse
Didn't you format persist by any chance unintentionally?
*Edit: Didn't see the next line. Are you sure the reflash was successful? My persist partition was also damaged somehow and had to reflash like 3 times. After that suddenly all sensors came back.
Yeah, the reflash didn't give me errors
Luigi2201 said:
Yeah, the reflash didn't give me errors
Click to expand...
Click to collapse
Were you able to solve? I have a similar problem. None of the sensors work, including the proximity sensor. Which file can be corrupted ?
Luigi2201 said:
Yeah, the reflash didn't give me errors
Click to expand...
Click to collapse
SOLVED.
The main problem was Persist.img
Related
I'm experiencing black screen during calls issues, which is usually a sign telling the proximity sensor is gone bonkers.
I have that on EOS/CM11/D.U
I have not flashed COS 2.0, baseband/modem are still out-of-the-box ones (COS 1.20)
I kinda remember there were some package I could flash to try fixing this before sending it for RMA
Could some one please help me ?
theradec said:
I'm experiencing black screen during calls issues, which is usually a sign telling the proximity sensor is gone bonkers.
I have that on EOS/CM11/D.U
I have not flashed COS 2.0, baseband/modem are still out-of-the-box ones (COS 1.20)
I kinda remember there were some package I could flash to try fixing this before sending it for RMA
Could some one please help me ?
Click to expand...
Click to collapse
Use the search function:
Flash the Original Oppo recovery, then install COS 2.0, then go to COS 2.03 (beta), then back to one of the 1.2.* versions (I did it with 1.2.6). NOW install TWRP and use your favourite ROM. Your issues will then be fixed.
As I read it on the Oppo forums, something in the calibration of the sensors changed when 2.0 was introduced. I have no idea what, but the above steps fixed the problem for me.
Thank you very much
I understood those steps were for those who wanted to use custom rom from CoS 2.0
Not that it could fix other issue
theradec said:
Thank you very much
I understood those steps were for those who wanted to use custom rom from CoS 2.0
Not that it could fix other issue
Click to expand...
Click to collapse
Damn, I should have read more attentively. Maybe you could still just go to COS 2.0, then to 2.03 and back? Might be that on the way your problem might get fixed?
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
bzadi said:
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
Click to expand...
Click to collapse
Probably the custom ROM causing the issue
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
I've got the exact same problem, now proximity sensor doesn't work at all
bzadi said:
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
Click to expand...
Click to collapse
Nvjoel said:
I've got the exact same problem, now proximity sensor doesn't work at all
Click to expand...
Click to collapse
Do you have any kind of screen protection?
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
Nope, no screen protector, no case.
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
No case and no screen protection.
Hey guys I'm sovan, lately I have been having some issues after installing a custom 8.1 rom on my device (pixel experience rom to be precise), I lost my VOLTE and couldn't get it back(my 4g lte connection was ok so I can use internet but couldn't call anyone) so I searched on some forum's regarding that issue, and I got some fixes but all of them required me to use a PC , 2 month ago I damaged my pc's motherboard so I couldn't use it fix my issue. Few days ago I downloaded magisk v16 zip and flashed that on my device after flashing it i rebooted my phone and saw I still didn't had my VOLTE back(not surprised coz thats rooting app). After that that I opened magisk app and gone to download section and looked for VOLTE disable module, after downloading and installing that module I restarted my phone and again there was no VOLTE, so I go to magisk again and uninstalled that VOLTE disable module and rebooted my phone and what u know I got my VOLTE back now I can call using VOLTE... after that happened I was a little sceptic so I power off my device and go to my bootloader using volume down plus power key and start my device and again I lost my VOLTE so I did everything what I did before installing VOLTE disable module and reboot then uninstalling that module and reboot after that I again got my VOLTE back...:fingers-crossed:
This is a temporary fix everytime u power off ur device u may lose ur VOLTE again if that happens just follow the same process....hope this helps
http://telegra.ph/Volte-Fix-For-Moto-G5-Plus-06-14-2
Sent from my XT1686 using Tapatalk
I suggest resolving VoLTE to create a back of EFS+Partition in a 7.0/7.1.2 custom rom (I personally stuck with 7.1.2 for my backups). Works like a charm when using the guide Prince153 has so generously shared.
Prince153 said:
Sent from my XT1686 using Tapatalk
Click to expand...
Click to collapse
I followed all steps that u mentioned above and did got my volte back so I restored my custom rom like u said and it works but Everytime I power off my device my volte gone,for getting it back I had to install a module or use kernal auditor and power off/on my device.(I don't have any backup of my stock rom or my efs folder).this issue keep coming back
sovanr7059 said:
I followed all steps that u mentioned above and did got my volte back so I restored my custom rom like u said and it works but Everytime I power off my device my volte gone,for getting it back I had to install a module or use kernal auditor and power off/on my device.(I don't have any backup of my stock rom or my efs folder).this issue keep coming back
Click to expand...
Click to collapse
Wait for 1-2 minutes for showing volte if it doesn't then you can turn on/off airplane mode or try enabling/disabling volte also take a backup of EFS on extsdcard
Sent from my XT1686 using Tapatalk
Prince153 said:
Wait for 1-2 minutes for showing volte if it doesn't then you can turn on/off airplane mode or try enabling/disabling volte also take a backup of EFS on extsdcard
Sent from my XT1686 using Tapatalk
Click to expand...
Click to collapse
Ok I'll try it next time I power off my phone...:good::fingers-crossed:
Prince153 said:
http://telegra.ph/Volte-Fix-For-Moto-G5-Plus-THAT-WILL-PERMANENTLY-SCREW-YOUR-PHONE!!!!
Sent from my XT1686 using Tapatalk
Click to expand...
Click to collapse
No no no no no!!!! Gosh why are people still posting this and other similar "fixes"! Do not ever flash another device's persist.
Please, this thread below is a sticky in this forum and explains why.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
NZedPred said:
No no no no no!!!! Gosh why are people still posting this and other similar "fixes"! Do not ever flash another device's persist. QUOTE]
Hi sir, I'm I did used prince153's method to to fix my issue before, and it's still not fixed my issue so I gone back to pixel experience rom and whenever I power off my device my volte goes away(I don't have any backup of my stock files so I opted for his method).I don't really know what to do so I try not to power off my device not really flashing any roms from then.... If lose my volte try wipe cache / dalvik cache and restart my device it works sometimes...if it doesn't work I flash the pixel rom again...then my volte usually comes back,I don't any hope for me to fix this issue permanently.....
Click to expand...
Click to collapse
sovanr7059 said:
NZedPred said:
No no no no no!!!! Gosh why are people still posting this and other similar "fixes"! Do not ever flash another device's persist. QUOTE]
Hi sir, I'm I did used prince153's method to to fix my issue before, and it's still not fixed my issue so I gone back to pixel experience rom and whenever I power off my device my volte goes away(I don't have any backup of my stock files so I opted for his method).I don't really know what to do so I try not to power off my device not really flashing any roms from then.... If lose my volte try wipe cache / dalvik cache and restart my device it works sometimes...if it doesn't work I flash the pixel rom again...then my volte usually comes back,I don't any hope for me to fix this issue permanently.....
Click to expand...
Click to collapse
Sorry to say this but you shouldn't have followed prince123's method, flashing some other persist will cause permanent problems.. in case you have flashed only efs you might have a chance of full recovery.
Click to expand...
Click to collapse
npradeeppai said:
sovanr7059 said:
Sorry to say this but you shouldn't have followed prince123's method, flashing some other persist will cause permanent problems.. in case you have flashed only efs you might have a chance of full recovery.
Click to expand...
Click to collapse
I followed every step...(at that time I was kinda desperate to fix my issue).I caused permanent DMG instead of fixing it i guess,I should've known better before proceeding it's my fault.anyways thanks for all information I appreciate it...:good:
Click to expand...
Click to collapse
NZedPred said:
No no no no no!!!! Gosh why are people still posting this and other similar "fixes"! Do not ever flash another device's persist.
Please, this thread below is a sticky in this forum and explains why.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Click to expand...
Click to collapse
When i first flashed custom rom i lost volte then i restored with this method
What's wrong with this method
Sent from my XT1686 using Tapatalk
Prince153 said:
When i first flashed custom rom i lost volte then i restored with this method
What's wrong with this method
Sent from my XT1686 using Tapatalk
Click to expand...
Click to collapse
Read the link I posted. Section 5a talks about the false impression of success.
sovanr7059 said:
npradeeppai said:
I followed every step...(at that time I was kinda desperate to fix my issue).I caused permanent DMG instead of fixing it i guess,I should've known better before proceeding it's my fault.anyways thanks for all information I appreciate it...:good:
Click to expand...
Click to collapse
Same here i did the same
Sent from my XT1686 using Tapatalk
Click to expand...
Click to collapse
I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Have the same problem. It has something to do with your persist partition. Perhaps you saved it via twrp? I had a save but don´t find it. **** happens.
I erased everything and flashed every fastboot rom via edl or normally. My fingerprint is broken!
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Veran125 said:
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Click to expand...
Click to collapse
In my case it´s a software issue... I used to open my phone, but when my fp broke when I was trying to fix goodix for our new bootleggers rom. I did the fix from official telegram group and a after that, root explorer could mount persist (this was the issue, why fp couldn´t be safed in gsi´s using a pie vendor), but the fp still couldn´t be safed. That means, now it could connect data and changed sth. badly...
I had the same problem. But I had a backup of the twrp sections of the persist and efs. I restored these partitions and flashed 9640 miflash. now the fingerprint works fine
So as long as my fingerprint sensor is recognized, it's most likely not a hardware issue? Furthermore did I unbrick my phone by flashing with EDL mode. Isn't everything formatted then? But I also downgraded to Oreo after that, could that be the reason?
Veran125 said:
But I also downgraded to Oreo after that, could that be the reason?
Click to expand...
Click to collapse
No
My fingerprint recognition works now with rr gsi. I will try wheather the problem is solved on stock too. I just went back too rr gsi, becouse I have a fully working data partition for it and luckily my fp started to work again. Idk what´s the problem.
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp - works for me!
https://forum.xda-developers.com/showpost.php?p=79368367&postcount=25
Thanks a lot, it really works.
Good that I wrote here before I reopened my phone.