Question Sensors stopped working - Xiaomi Poco X3 Pro

For some strange reason, the sensors stopped working. I tried reinstalling vanilla MIUI, but it didn't bring results. How can this be fixed ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
12-09 18:51:19.408 931 2315 W HidlServiceManagement: Waited one second for [email protected]::ISensorManager/default
12-09 18:51:19.408 649 649 I hwservicemanager: Since [email protected]::ISensorManager/default is not registered, trying to start it as a lazy HAL.
12-09 18:51:19.408 931 2315 I HidlServiceManagement: getService: Trying again for [email protected]::ISensorManager/default...
12-09 18:51:19.408 649 2549 W libc : Unable to set property "ctl.interface_start" to "[email protected]::ISensorManager/default": error code: 0x20

ServOKio said:
For some strange reason, the sensors stopped working. I tried reinstalling vanilla MIUI, but it didn't bring results. How can this be fixed ?
View attachment 5478537
Code:
12-09 18:51:19.408 931 2315 W HidlServiceManagement: Waited one second for [email protected]::ISensorManager/default
12-09 18:51:19.408 649 649 I hwservicemanager: Since [email protected]::ISensorManager/default is not registered, trying to start it as a lazy HAL.
12-09 18:51:19.408 931 2315 I HidlServiceManagement: getService: Trying again for [email protected]::ISensorManager/default...
12-09 18:51:19.408 649 2549 W libc : Unable to set property "ctl.interface_start" to "[email protected]::ISensorManager/default": error code: 0x20
Click to expand...
Click to collapse
Find Xiaomi repair center for warranty repair and checkup.

pl1992aw said:
Find Xiaomi repair center for warranty repair and checkup.
Click to expand...
Click to collapse
Are there really no other solutions to the problem ? I bought the phone about three weeks ago and I very much doubt it's a hardware problem
logcat
https://cdn.discordapp.com/attachments/906638910426329091/918910357941141534/logcat.txt

I found a solution to the problem
As it turned out, this is a fairly common problem for poco x3 pro users. For the solution you need to flash persist. The easiest way is to use the adb shell on your computer when recovery is running and do the following:
Create a copy (just in case!)
Code:
dd if=/dev/block/by-name/persistbak of=/sdcard/persistbak.img
flash persist:
Code:
dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist
now you can reboot into the system and everything should work
original post

ServOKio said:
Are there really no other solutions to the problem ? I bought the phone about three weeks ago and I very much doubt it's a hardware problem
logcat
https://cdn.discordapp.com/attachments/906638910426329091/918910357941141534/logcat.txt
Click to expand...
Click to collapse
I usually rule out hardware problem first, which may expire when the warranty ends.
If you are unlucky, then eventually you still will need to go to find the repair center.
Good to know you got the sensors back.

No miracles - yes, the sensors are working, but the distance sensor always shows the same value

Related

[Q] Trouble on AAHK: sudo adb shell mount -o rw /dev/block/mmcblk0p25

Hi Droidy types.
Phone: HTC Inspire 4G
OS: 2.3.3
Carrier: AT&T
Using PD98IMG.zip: No.
First time rooter, here. I tried following some other instructions, but the psneuter step failed, saying: "Failed to set prot mask (Inappropriate ioctl for device)". Then I found the excellent AAHK script.
Everything seemed to go well, until the step that says:
Error opening copy file.
^^^^^^^^^^^^^^^^^^^^^^^^
I- NORMAL ERROR HERE -I
error: device not found
Checking adb connection....
Usage: mount [-r] [-w] [-o options] [-t type] device directory​
...then it's pretty much one error after another. You can see the full report, here: gist.github.com/2b25350305da5d727ff1 {Sorry about the non-link. "New Users" rule in effect} (the above chunk starts at line 257.)
Basically the first line of the script that fails is:
sudo adb shell mount -o rw /dev/block/mmcblk0p25
After it ran, I went ahead and did the step from the manual that says "How to tell if the hack kit really worked" -> "adb reboot recovery".
This gave me a boot screen that showed this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To which I had to VolUp + PwrOn to restart.
Now it is caught in an infinite loop on bootup, which according to "adb logcat" seems to be having trouble here:
I/DEBUG ( 1216): pid: 1218, tid: 1218 >>> zygote <<<
I/DEBUG ( 1216): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad​
(A sample of the logcat is here: gist.github.com/caabe7212f6c651cdbe4 (the above lines start at line 34). It is only a sample because... it keeps looping forever. =))
I saw something on a different site saying something to the effect that a segfault in zygote means the system is borked, and that it is a simple program that shouldn't be crashing.
Any advice?
-rking
P.S.: Thank you so much!
The effin manual is all you need to read. It worked flawlessly for me. What kind of microSD card do you have? That could be your problem or you may have missed a step in set up.
Sent from my Inspire 4G using Tapatalk 2
You should hit the IRC channel that is for that purpose. Without the whole cmd session is hard to know what failed. Anyway, your issue might be connection issues, so fix that and re run the kit
Sent from my Desire HD using XDA
Yeah!
I ran the AAHK again, even with my phone sitting there, refusing to boot.
It not only got past the step where I had the error before, but sailed through doing everything else.
This is amazing -- my phone is mine, now.
Thanks so much!
-rking
ryanjking said:
I ran the AAHK again, even with my phone sitting there, refusing to boot.
It not only got past the step where I had the error before, but sailed through doing everything else.
This is amazing -- my phone is mine, now.
Thanks so much!
-rking
Click to expand...
Click to collapse
Glad you are back...enjoy!
ryanjking said:
I ran the AAHK again, even with my phone sitting there, refusing to boot.
It not only got past the step where I had the error before, but sailed through doing everything else.
This is amazing -- my phone is mine, now.
Thanks so much!
-rking
Click to expand...
Click to collapse
Glad to hear you figured it out.
Sent from my Inspire 4G using Tapatalk 2
Please, fully read AAHK readme before use it, this problemm fully described in manual, good for you, that everything fine gor you, but pay attantion at the next time
Jsergan, if u have read you would have seen that the issue was solved. Stop posting to get the 10 posts...
Sent from my Inspire 4G using XDA

Samsung galaxy s7 sm-g930fd stuck on bootloader exeption

SAMSUNG GALAXY S7 DUAL SIM MODEL: SM-G930FD STUCK ON BOOTLOADER EXEPTION, I HAD IT CHARGING LIKE ALWAYS IN THE MORNING WITH THE PHONE ON AND SUDDENLY IT FROZE, SO I TRIED RESTARTING THE PHONE, IT STAYED ONLY STUCK ON SAMSUNG LOGO, SO I TRIED NEXT IS PUTTING THE PHONE IN DOWNLOAD MODE AND IT WORKED BUT I HAD TO DOWNLOAD THE FIRMWARE, SO I HAD TO LEAVE TO WORK LEAVING MY PHONE AT HOME, I COME BACK HOME AND THIS SHOWS UP:
Bootloader Exeption
{ RST_STAT = 0x10000 }
EVT 1.0
ASV TBL VER = 8, GRADE = C
ECT = PARA005E
LOT_ID: NA2PA
CHIP_ID : 0274cdce869c
CHIP_ID2: 0000000
MNGS: 37'C APOLLO: 38'C G3D: 38'C ISP:40'C
Exeption: do_handler_serror: SERROR(esr: 0xbf000000)
0
pc : 0x8f0131d0 lr : 0x8f022b7c sp : 0x8f10fe90
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I HAVENT INSTALLED ANY RECENT APPS, NOR ROOTED THE PHONE, EVERYTHING HAS STOCK ORIGINAL FIRMWARE
PLEASE HELP ME!!!!!!!!!!!!!!!!!!!!!!!!!!
Sm-g930fd stuck on bootloader
mikangelo38 said:
SAMSUNG GALAXY S7 DUAL SIM MODEL: SM-G930FD STUCK ON BOOTLOADER EXEPTION, I HAD IT CHARGING LIKE ALWAYS IN THE MORNING WITH THE PHONE ON AND SUDDENLY IT FROZE, SO I TRIED RESTARTING THE PHONE, IT STAYED ONLY STUCK ON SAMSUNG LOGO, SO I TRIED NEXT IS PUTTING THE PHONE IN DOWNLOAD MODE AND IT WORKED BUT I HAD TO DOWNLOAD THE FIRMWARE, SO I HAD TO LEAVE TO WORK LEAVING MY PHONE AT HOME, I COME BACK HOME AND THIS SHOWS UP:
Bootloader Exeption
{ RST_STAT = 0x10000 }
EVT 1.0
ASV TBL VER = 8, GRADE = C
ECT = PARA005E
LOT_ID: NA2PA
CHIP_ID : 0274cdce869c
CHIP_ID2: 0000000
MNGS: 37'C APOLLO: 38'C G3D: 38'C ISP:40'C
Exeption: do_handler_serror: SERROR(esr: 0xbf000000)
0
pc : 0x8f0131d0 lr : 0x8f022b7c sp : 0x8f10fe90
I HAVENT INSTALLED ANY RECENT APPS, NOR ROOTED THE PHONE, EVERYTHING HAS STOCK ORIGINAL FIRMWARE
PLEASE HELP ME!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I have the same issue ,please tell me if you solved that

Understanding S1 Service mode

Can anyone help to understand S1 Service mode (not a fastboot) ?
For example, Sony device [ vid: 0FCE ; pid: ADDE ] also like [ SOMC Flash Device ]
Where I can get more information about this ? from what to start ? something about structure / commands etc. Would be great to see anything without sniffing and debugging usb traffic <_<
Can I, for example, push bootloader into RAM then access to its commands such as loading something into addrX then to start evaluation from that addrX and so on. How about without emmc (CPU + RAM only) ? How about u-boot?
I started from problem here (I also have trim-area (TA) backup, but...):
https://forum.xda-developers.com/showpost.php?p=76505189&postcount=714 (phone is not mine)
Mainly I can't think of how I can inspect emmc on hardware problems without soldering at all because I have no Z3X or something else. So I can programming only via USB and some other related things if it's not so hard to prepare at home manually.
Anyway, would be great to solve or at least understand this problem in details.
So any suggestions for more understanding this bug or S1 Service are very welcomed!
Well, looks like emmc is dead. Don't know why ( Samsung KLMAG2GEAC-B001 ).
Unfortunately, but I still have no any information about mentioned S1 mode. Thus I can't understand is it possible to redirect most common requests for emmc to sd card.
That is, something like to use preloader for allocating in upper range of RAM the our modified loader. Then writing and running at this address which will provide information about emmc from another way. +TA/Boot/...
hmm, I think I will not spend my time for this device today anymore However, any info about S1 still is actual of course.
ah yes, don't know the good place for writing about the following tips below (move it if you need). Just my bonus for everyone when I was checking mentioned device above:
[ Sony Xperia Z Ultra C6833 ]
* Found UART:
1. RX
2. TX
3. GND
4. VCC is not required.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
* Solution to charge the Xperia Z ultra battery with very low voltage (less than 2.6v etc) without phone but still through battery controller:
! Strictly observe the polarity of the connection. Otherwise it will be corrupted. !
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3.8+ it's okay now:
Click to expand...
Click to collapse
* About Test-point you should already know where it placed from other topics otherwise, find the red dot from first image above

[Request] persist.img for OnePlus 8 EU

Hi,
My fingerprint sensor stopped working after restore clean rom and relock the bootloader .
I think reflashing the persist partition will fix this. I already have tested the unbrick tool and this don't worked.
So can someone please share their persist partition with me, you can use this app to extract it:
https://play.google.com/store/apps/details?id=ma.wanam.partitions
or ADB command :
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit
Click to expand...
Click to collapse
I'm running Oxygen OS version 10.5.4.IN21BA
My phone model is: IN2013
Thanks
Hey man, what happened did you solve the issue? or what, my fingerprint is also broken
I sent it to after-sales service.
The UPS guy picked it up at my house on Tuesday morning. And it was returned to me repaired this Thursday morning, two days later, which is extremely fast.
So if your oneplus is guaranteed, don't bother with it and send it to service.
Hello !
Can you send a dump of your **persist.img** ? I have downgrade my phone from android 12 to android 11 due to a critical crash but my persist is now dead.
Regards
Hello !
I have found a way to fix the fingerprint reader without any backup of the persist.img. At the first my OnePlus 8 EU IN2013 was reset with MSM tool. So the fingerprint system is KO. To reinstall the fingerprint system, you need to:
1) Enable the OnePlus FactoryMode (EngineeringMode)
1.a) On the phone type the phone number
Code:
*#06#
and copy the IMEI1
1.b) Go to https://one.andro.plus/ and select Unlock for 10 minutes and type your IMEI1
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.c) Type the phone number
Code:
*#*#5646#*#*
then exit the qrcode scanner by pressing back and type the generated code found on one.andro.plus
Spoiler
2) Now the EngineeringMode is unlock, use the phone number
Code:
*#808#
to open it. (see
Spoiler
)
3) Go to Debuging Device > Finger Print Test > Finger print calibration test (Pure White - 90% Blue)
4) Click on Start Test. It may print an error at the first time but try it again.
5) Click on Flesh Rubber Sleeve Test1, wait the first test and then PUT YOUR FINGER ON THE READER AND KEEP IT'S OVER
6) Click on Black Rubber Sleeve Test and DO NOT TOUCH THE READER
7) Click on Positionning Circle Test and PUT YOUR FINGER ON THE READER AND KEEP IT'S OVER
8) At the end there is an error but it's fine And the fingerprint reader now works

Oneplus 8 dead after try unlock bootloader

Op8 i think its was T or V
But after try to unlock bootloader its bricked and now not taking any flash file
I tried many file but the only one error
Trg id error
So i try with smt even with imei loss risk
And the result was as you see in pick
But the worst thing is smt erase all luns
And now my device's is total empty
But just detect 9008
So is there anyway or anyone can fix?
I want to know is there anyway to bypass this id chk? Or direct flash or something?
No worry about payment
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There should be not be "COM32", or generally any number higher than 6. Check to see if your drivers are defect and try flashing again.
Xryphon said:
There should be not be "COM32", or generally any number higher than 6. Check to see if your drivers are defect and try flashing again.
Click to expand...
Click to collapse
Bro its not issue com Port i flash many time in higher port
Even in this case smt detect and erase all partitions then stuck
Trg id should not be default
Or 0
@Whoareyou
See this bro
Mr Hassan said:
Op8 i think its was T or V
But after try to unlock bootloader its bricked and now not taking any flash file
I tried many file but the only one error
Trg id error
So i try with smt even with imei loss risk
And the result was as you see in pick
But the worst thing is smt erase all luns
And now my device's is total empty
But just detect 9008
So is there anyway or anyone can fix?
I want to know is there anyway to bypass this id chk? Or direct flash or something?
No worry about paymentView attachment 5644461
Click to expand...
Click to collapse
I can help u with it.
Prinçe çharming ap said:
I can help u with it.
Click to expand...
Click to collapse
You can text me on my Telegram to get faster replies.

Categories

Resources