Related
Hola Devs,
Currently I own Mi 5 in which I used to have Lineage os 14.1. But after the recent update i.e Lineage-14.1-20180110 nightly gemini, all of the sensors got pissed of except fingerprint sensor.
Initially I thought it may a hardware problem, but after brown through the root files, I got to find that all my sensor related files are missing from the Persist partition. So I downloaded the fastboot rom the official website and flashed through Mi Flash Tool in both Fastboot and EDL mode. still the problem remains as it is. While flashing, the tools is not even considering the Persist.img file. BTW I even tried to flash through Fastboot cmd, and it is showing error as the partition is write protected, neither the partition is erasing nor is flashing
Can I get any kind of solution??
Or can you provide me the persist flash bat file formatting or flashing the persist Img file.
Or can you guys provide me sensor related files to be placed wherever it is necessary..
BTW wifi Bluetooth nfc fpc all are working except Gyro sensor and Proximity sensor. And also it is not at all showing in Engg mode too(*#*#6484#*#*)
thank in advance
It's the persist partition problem.
You could refer to this thread
http://www.miui.com/thread-6788019-1-1.html
Unfortunately, the language is Chinese. Please use the translator if you can't read it. Of course, you could ask me how to do it too.
Sorry, I am a Chinese, so I may have made some mistakes in grammar. Hope you could understand what I am saying ?
Ask someone to backup him persist with zcx recovery, then restore yours with it and problem solved.
I had exactly the same problem as you and that fixed mines.
Greetings
So after trying Xiaomi EU, MiGlobe Rom and Android Q Beta
I decided to flash back to MIUI 10.3.8 via fastboot
Somehow my front camera won't open properly, it kept saying "Can't open front camera, please calibrate".
And when I press Calibrate, popup cam goes up and down 3 times in a row and says "Can't calibrate".
Any idea how to fix this?
EDIT: Must be the fastboot rom I downloaded. Other rom's front cam worked fine...
I am having same issue. Initially I thought it was hardware problem.
But I noticed it seem to be related to software.
Took few restart of camera app and sometime phone restart, for it to work
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
LogicalMaverick said:
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
Click to expand...
Click to collapse
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Robbo.5000 said:
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Click to expand...
Click to collapse
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
What's LR?
degeaba1981 said:
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
What's LR?
Click to expand...
Click to collapse
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Robbo.5000 said:
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Click to expand...
Click to collapse
Problem solved! I flashed via miflash the Chinese rom, in fastboot and the front camera was working. Then I've put the Indian global version and front camera is working fine now.
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Ekalous said:
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Click to expand...
Click to collapse
I have the same problem. I'm trying to solve it but nothing for now!
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
topaloglu321 said:
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
Click to expand...
Click to collapse
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
znsvs123 said:
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
Click to expand...
Click to collapse
You can't show them up. The only way is to change TWRP, hoping that is supported
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
I'll try this thank you.
thelegoboy said:
You can't show them up. The only way is to change TWRP, hoping that is supported
Click to expand...
Click to collapse
thanks, not all of twrps are built equally. :good::good::good:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
i fixed that problem just flashing chinese.rom via miflash and.camera pop up working again
sagar.anits said:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
Click to expand...
Click to collapse
Same problem here
RAJIB AHMED0077 said:
Same problem here
Click to expand...
Click to collapse
try flashing 10.3.16 chinese rom via fastboot yesterday i flash that rom and it fix that problem in my k20 Pro
After boot the accelometer stops working after a few minutes, so autorotation is not functional.
I found that this i maybe a bug in miui 10 and also other devices, some users say when you google this error.
IT seems to have to do with autobrightness setting. I tried some things but did not find a solution yet.
eg I tried this: http://en.miui.com/thread-458462-1-1.html
My question is, is this still a bug or I am the only one who has this issue?
I am facing the same issue. What ROM are you using?
kltos said:
I am facing the same issue. What ROM are you using?
Click to expand...
Click to collapse
I´m on raphael_eea_global_images_V10.3.1.0.PFKEUXM. There is an update to V10.3.3.0.PFKEUXM, but this has problems with TWRP and I need this.
A solution for many ist, that the persist.img has an error and to flash persist.img again through TWRP or fastboot. But when doing this I get an error "partition is write protected".
Look here: http://en.miui.com/thread-312976-1-1.html
Maybe a dirty flash of the full rom is a solution, but I have never made this.
It has something to do with automatic brightness. I also tried this, but didn´t work:
http://en.miui.com/thread-458462-1-1.html
It´s important to know if this is a general bug or we need to flash rom again. I don´t know....
franky_z said:
I´m on raphael_eea_global_images_V10.3.1.0.PFKEUXM. There is an update to V10.3.3.0.PFKEUXM, but this has problems with TWRP and I need this.
A solution for many ist, that the persist.img has an error and to flash persist.img again through TWRP or fastboot. But when doing this I get an error "partition is write protected".
Look here: http://en.miui.com/thread-312976-1-1.html
Maybe a dirty flash of the full rom is a solution, but I have never made this.
It has something to do with automatic brightness. I also tried this, but didn´t work:
http://en.miui.com/thread-458462-1-1.html
It´s important to know if this is a general bug or we need to flash rom again. I don´t know....
Click to expand...
Click to collapse
Thanks for the insight.
(I flashed latest fastboot rom using miflash tool and auto rotate was broken.)
Flashing persist.img has done the trick. My problem is solved.
Here is what I did:
My device is raphaelin, that is k20 pro Indian.
I downloaded latest fastboot rom for raphaelin and extracted persist.img and flashed it using TWRP 3.3.1-15 Unofficial by mauronofrio. Problem solved.
Hope the same works for you.
kltos said:
Thanks for the insight.
(I flashed latest fastboot rom using miflash tool and auto rotate was broken.)
Flashing persist.img has done the trick. My problem is solved.
Here is what I did:
My device is raphaelin, that is k20 pro Indian.
I downloaded latest fastboot rom for raphaelin and extracted persist.img and flashed it using TWRP 3.3.1-15 Unofficial by mauronofrio. Problem solved.
Hope the same works for you.
Click to expand...
Click to collapse
Thanks for the help. I´m on Fox Recovery, it did not work, I will try TWRP...
franky_z said:
Thanks for the help. I´m on Fox Recovery, it did not work, I will try TWRP...
Click to expand...
Click to collapse
No problem . Let me know if that works.
kltos said:
No problem . Let me know if that works.
Click to expand...
Click to collapse
Flashed TWRP you mentioned, flashed pesist.img and sensors work again. Before that, front camera calibratet itself , but then everything works :good:
Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
gamerboy_010 said:
Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
Click to expand...
Click to collapse
very unusual sounding problem ...sounds like you tried to play around with vendor props and to make aux camera working
flash stock using miflash ...do it in edl mode using fastboot
fastboot oem.edl
when finished ...BOOT not flash orange fox revovery
fastboot boot recovery.img
*"might be different command depending on pc amd name and location of downloaded recovery
then use a persist restorer flashable zip you can.find in jasmine/wayne official telegram.group and flash that ..
them reboot and use as normal
Thanks, i will try and rever
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
gamerboy_010 said:
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
Click to expand...
Click to collapse
yeah no bro that is impossible even if nothing is impossible that is 99% impossible and you didn't do everything that i suggested
make a video of the problem and a video of applying my fix
if not i can't help you further ..
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
gamerboy_010 said:
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
Click to expand...
Click to collapse
what device are you using ?
jasmine or wayne
which recovery did you use ?
_what i can tell you is not all twrp recovery works or can flash persist
_ try to use orange fox but use another recovery that can backup and flash persist ..
press
mount button ...if you don't see persist partition option here the recovery can not flash it even if .zip seems to flash well
look for pie persist.img for your device according to if it is jasmine or wayne ...look for recovery that can mount, backup and flash .img files to persist
---------- Post added at 09:01 PM ---------- Previous post was at 08:42 PM ----------
use these files bro
https://www.dropbox.com/s/w2d2z92yn6115ot/persist.img?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0
https://www.dropbox.com/s/or0n7b6hxagr2ee/4_6050642049911227980.zip?dl=0
if you have jasmine flash persist in both slots
Thanks, i have jasmine. Let me use your files and revert.
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
gamerboy_010 said:
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
Click to expand...
Click to collapse
flash stock rom but in edl mode , using Miflash. Use the cmd :
fastboot oem edl
_dont use custom rom
_dont flash in normal fastboot
the only way this problem could be happening is if you were trying modifications in vendor and when you flash a new rom it doesn't overwrite the changes because it is modifying only vendor ...flashing custom roms in recovery won't help , neither will stock in fastboot mode . Only edl mode .... furthermore directly after flashing stock ...flash persist ...that way you start 100% fresh ..if it still doesn't work it is hardware failure
but i can do nothing more for you unless you send videos or photos of you following the steps and the problem with the camera .
**if you know how try removing back and enter edl with testpoint ...flash ... disconnect cameras and reconnect them ... then start phone
***if you remember what you changed just change it back ( did you try modifications? , what did you do ?)
****copy vendor files for camera from friend
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
no problem man glad you succeeded ... probably it worked but after flashing persist everything usually starts working Normally after a few reboots ..so probably by then it was when you flashed derp
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
today i experienced a funny situation ...i took the new stock update for wayne and then i had the same camera problem ..
after thinking a little i realised it was after uodate so i had to just reapply the api2 for camera and then it started working normally so in future before going the long way make sure to enable api2 again after you update or flash a new thing . if camera works great if not take the long way...
I recently bricked my RN10s and then had to flash stock ROM using the SP flash tool now the sensors are not working properly.
The device turns its screen on and off because it thinks it's being picked up.
The sensors used by google maps show that I'm rotating constantly.
I am new while flashing on A/B partitions and thus ended up bricked, any help will be highly appreciated. I was trying to flash pixel 4 android 13 GSI A/B and also tried dot os but it seems like my device's flash memory after the brick is not working properly because it does not boot into custom twrp by the command Fastboot boot TWRP.img.
looking forward.
flash stock rom and done
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
dequr said:
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
Click to expand...
Click to collapse
I think it might be due to corrupted persist partition, I never custom romed a device but have been researching for my RN10s and I read that persist contains the sensor data control and l1 certification that's why you need to back it up in case it corrupts. Sadly you can't flash persist from the internet since it's unique to every phone if you flash it you loose l1 certification forever but get back sensor functions (I am not sure about sensor functions returning)
Also there is a tool to fix corrupted persist so do research it but whatever you do make sure you are 100% certain it's what you want changes to persist are permeant (except if you backed up persist before the brick in which case just flash the persist backup)
V.I: as I said I never flashed a device and don't know much about it this is what I read through reddit and research, take it with a grain of salt and do your own research aswell
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
dequr said:
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
Click to expand...
Click to collapse
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Okay will try this now truly appreciate the support thx. Tho the phone is working quite better by time apart from the sensors.
The degree sensor or smt like that is just increasing to 360 and then will start from 0 again
killer_v41 said:
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
Click to expand...
Click to collapse
A
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Any suggestions form where to download because there are lot of sites available
This is the sensor data and as you can see Orientation sensor along with the rotations third value and the z axis of gyroscope and accelerometer isn't working well so ill re-flash with the first miui this phone had and apply updates on it hopefully it will fix the errors.
Your browser is not able to display this video.
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
alright so I was going thru the images and I couldn't find any persistence in both 13.0 and 12.5 but now as I am now the question is how are the x and y axis keeping their value correct while z isn't so will tho ask for a persist file but just curious how is it detecting sensors then ??
dequr said:
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
Click to expand...
Click to collapse
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
killer_v41 said:
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
Click to expand...
Click to collapse
Yea I discovered the fastboot ROM didn't have persist.img and I've stopped trying because the gsi has detected it and some how some things have been fixed I've also seen. File named gsi_persist_data in /data nvr opened it but gyroscope while gaming doesn't stop and raise to wake works.