Related
hello XDA people.
so, first lets go with the specs of my phone
P8lite ALE-L21
android 6.0
emui 4.0.3
C432B608
now, for the real question.
whenever I try to call someone, my call automatically cancels (drops)
but, here's the funny part, the sms are working fine, and other people can call me too.
here's what I've tried:
cleared cache+dalvik using TWRP = no result
re-flashing the image of boot, cust, and system using fastboot = no result
the ONLY thing that helps (for a breaf period of time) is making a factory reset
but then again, after I reset it, the same problem shows up in about 2 days, idk what should I try.
maybe someone else had/has this problem and you know how to fix it?
thanks in advance!
konopla4 said:
hello XDA people.
so, first lets go with the specs of my phone
P8lite ALE-L21
android 6.0
emui 4.0.3
C432B608
now, for the real question.
whenever I try to call someone, my call automatically cancels (drops)
but, here's the funny part, the sms are working fine, and other people can call me too.
here's what I've tried:
cleared cache+dalvik using TWRP = no result
re-flashing the image of boot, cust, and system using fastboot = no result
the ONLY thing that helps (for a breaf period of time) is making a factory reset
but then again, after I reset it, the same problem shows up in about 2 days, idk what should I try.
maybe someone else had/has this problem and you know how to fix it?
thanks in advance!
Click to expand...
Click to collapse
Boot in safe mode and see if in that mode you can call
RootingPro-18 said:
Boot in safe mode and see if in that mode you can call
Click to expand...
Click to collapse
it's the same in safemode.
any other ideas? what this could be?
by the way, I CAN call emergency numbers, like 911 e.t.c
konopla4 said:
it's the same in safemode.
any other ideas? what this could be?
by the way, I CAN call emergency numbers, like 911 e.t.c
Click to expand...
Click to collapse
Buy new sim card, dear friend?
RootingPro-18 said:
Buy new sim card, dear friend
Click to expand...
Click to collapse
The funny part is that the sim is new
Are you using xposed?
---------- Post added at 20:58 ---------- Previous post was at 20:54 ----------
I know this may be stupid idea, could you check you have given all needed permissions for caller etc. If i remember right, there is permission "Make calls" or something like that
Vika__ said:
Are you using xposed?
---------- Post added at 20:58 ---------- Previous post was at 20:54 ----------
I know this may be stupid idea, could you check you have given all needed permissions for caller etc. If i remember right, there is permission "Make calls" or something like that
Click to expand...
Click to collapse
no, I'm not using xposed, and permissions were all set correctly!
okay so...
I tried dialing *#*#2846579#*#*..guess what...
vendor: vendor country file not exist
country: vendor country file not exist
okay, does anybody know how to fix this?
Quick update of what I just did!
I downloaded the APP file of my current build. and re-updated the phone using the stock recovery.
the vendor files seem to be in place, but I still cant make calls :/
I'll try making a factory reset later on.
@persona78 i hope you can help this guy
konopla4 said:
okay so...
I tried dialing *#*#2846579#*#*..guess what...
vendor: vendor country file not exist
country: vendor country file not exist
okay, does anybody know how to fix this?.
Click to expand...
Click to collapse
Hi! doens´t have it to when i type that code... so that is not the problem.
Do this:
Enable debug mode and plug usb to PC
Type this ->
Code:
adb shell getprop > c:\phone.prop
In PC on c:\ you will get a file
Code:
phone.prop
, use notepad++ and open that file.
Seek for this lines:
Code:
ro.hw.country
ro.hw.custPath
ro.hw.vendor
What say in this lines????
.
konopla4 said:
The funny part is that the sim is new
Click to expand...
Click to collapse
Check call barring settings.
persona78 said:
Hi! doens´t have it to when i type that code... so that is not the problem.
Do this:
Enable debug mode and plug usb to PC
Type this ->
Code:
adb shell getprop > c:\phone.prop
In PC on c:\ you will get a file
Code:
phone.prop
, use notepad++ and open that file.
Seek for this lines:
Code:
ro.hw.country
ro.hw.custPath
ro.hw.vendor
What say in this lines????
.
Click to expand...
Click to collapse
ro.hw country [EU]
ro.hw.custPath [/cust/hw/eu]
ro.hw.vendor [hw]
but, I found this line
Code:
[ro.baseband]: [unknown]
is it something I should be worried about?
kilroystyx said:
Check call barring settings.
Click to expand...
Click to collapse
everything is turned off, it is as it should be.
konopla4 said:
ro.hw country [EU]
ro.hw.custPath [/cust/hw/eu]
ro.hw.vendor [hw]
but, I found this line
Code:
[ro.baseband]: [unknown]
is it something I should be worried about?
Click to expand...
Click to collapse
Check your cust, see if you have a folder hw and inside a folder eu.
.
so, end to end I did to a factory reset.
THE CALLS ARE WORKING!
but I wonder...for how long?
so, the conclusion is - the only way to fix this (for now) is to do a factory reset (good thing I did a backup )
konopla4 said:
so, end to end I did to a factory reset.
THE CALLS ARE WORKING!
but I wonder...for how long?
so, the conclusion is - the only way to fix this (for now) is to do a factory reset (good thing I did a backup )
Click to expand...
Click to collapse
That was the next step i gonna tell if everything was fine in cust folder.
You use the default Huawei recovery to do the reset? Is better.
.
persona78 said:
That was the next step i gonna tell if everything was fine in cust folder.
You use the default Huawei recovery to do the reset? Is better.
.
Click to expand...
Click to collapse
before I did the factory reset, I had to flash the stock recovery. then I did the reset. then the next thing I did was install the TWRP
I'm having a problem with my Hawaii whenever I make call i can hear the other person but the person I'm calling doesn't hear me please help...
This is app for search meizu firmware and delete chinese apps
I use it to find daily updates
To get tips, make a long tap on the input field
To download the firmware, you first need to find it, then you need to click the "view" button and click on the link below.
After installation, you can get the root and delete the Chinese applications by script, for this you need to click the ". . ."
The source code is on github: https://github.com/YouROK/FlymeFirmwareChecker
Changelog:
1.04
- Added some devices to autocomplete
- Added some apks to remove script
- Added translation to release notes (Orig/En/Ru)
hi there. as i can see from Attached Thumbnails you are running nougat . can you please tell me if the heart rate sensor works?
Thank you..
ps have you tried the Flyme 6.2.0.0A version?
I use daily nougat. Sensors works well
heart rate sensor on home button
hi again please tell me if the heart rate sensor on home button works. because on global rom it is not.
thank you
Vasilislarisa said:
hi again please tell me if the heart rate sensor on home button works. because on global rom it is not.
thank you
Click to expand...
Click to collapse
Yes, work on daily
heart rate sensor on home button
hi.
thank you .
another ?. do you use a custom recovery as TWRP?
IF yes can you please upload?
i am on 6.1.0.0 global
if i update to 6.2.0.0 cn is there a choice to choose english language during setup?
how to uninstall all the Chinese apps?
can i have weather update for europe and my country? Greece?
thank you.
help
i upgrade to 6.2.0.0
i installed supersu 2.79
and after reboot stucked on boot screen
i entered recovery i tried to copy the update file but when the process started it ended with a message no firmware found
any suggestions?
thank you
Vasilislarisa said:
i upgrade to 6.2.0.0
i installed supersu 2.79
and after reboot stucked on boot screen
i entered recovery i tried to copy the update file but when the process started it ended with a message no firmware found
any suggestions?
thank you
Click to expand...
Click to collapse
SuperSU not support nougat(7.0).
You must now enter the recovery mode (volume + and power), connect the phone to the computer by usb, a disk will appear, copy the firmware and flash the phone.
On android 7+ you can not use supersu
help
thank you
i have done this, but on windows i get a error message saying that this file have properties that canot copy . if i continue the file disapearr . i tried this and on a mac with no luck
any suggestion
thank you
Vasilislarisa said:
i upgrade to 6.2.0.0
i installed supersu 2.79
and after reboot stucked on boot screen
i entered recovery i tried to copy the update file but when the process started it ended with a message no firmware found
any suggestions?
thank you
Click to expand...
Click to collapse
I'm haven't windows and Mac, in Linux all fine. The file copied to the phone is temporary, it disappears after reboot
thank you fried
I finally restored it. so I am good now.
thank you so much
Hi again.
My phone is OK now.
Please tell me if there is another dialer to use because I want to have big photo of the contact when I make a call
Thank you
Vasilislarisa said:
Hi again.
My phone is OK now.
Please tell me if there is another dialer to use because I want to have big photo of the contact when I make a call
Thank you
Click to expand...
Click to collapse
I use the standard dialer
Hi dear friend
You said that on Nougat I can not use supersu
Is there another app like this to use because I want to use a file explorer like es file and give root permitions.
Is there a chance to unlock bootloader?
Can I use a custom recovery like twrp
Vasilislarisa said:
Hi dear friend
You said that on Nougat I can not use supersu
Is there another app like this to use because I want to use a file explorer like es file and give root permitions.
Is there a chance to unlock bootloader?
Can I use a custom recovery like twrp
Click to expand...
Click to collapse
Use root from settings. Recovery is locked in pro6+ and not support custom recovery
thank you so much
need a root access?
No
Anyone mind sharing the original face unlock apk for me from the device's sytem files? Tried several versions already from APKMirror but all of them would force close.
Face unlock included in stock ROM.
jimmy123322 said:
Face unlock included in stock ROM.
Click to expand...
Click to collapse
Yes I know that, but I overwritten it with a different apk that's why I cant get it back now.....
Please someone with root willing to do this? Its located under \system\app\facelock\facelock.apk, then mind sharing it on google drive, dropbox, any other mirror service?
Instead of putting "unknown" files to your system, rather flash stock system image via fastboot. This way you'll have surely unmodded file with correct permissions.
_mysiak_ said:
Instead of putting "unknown" files to your system, rather flash stock system image via fastboot. This way you'll have surely unmodded file with correct permissions.
Click to expand...
Click to collapse
Done that, wouldn't help. Used the xiaomi tool.
Wait what? There's a face recognition unlock app? I don't have this, i just got the phone ( international version )
Try using smart lock's trusted face feature in security option..
Hope you'll be satisfied.
Roykooiman said:
Done that, wouldn't help. Used the xiaomi tool.
Click to expand...
Click to collapse
Don't understand how reflashing didn't help, but here you go.. https://expirebox.com/download/68d88b13e29f15961685143c34ffc859.html
_mysiak_ said:
Don't understand how reflashing didn't help, but here you go.. https://expirebox.com/download/68d88b13e29f15961685143c34ffc859.html
Click to expand...
Click to collapse
Thanks man! But still not working, have to try stock image again
May I ask what are you trying to do?
_mysiak_ said:
May I ask what are you trying to do?
Click to expand...
Click to collapse
Trying to get face unlock to work.
Roykooiman said:
Trying to get face unlock to work.
Click to expand...
Click to collapse
When does it crash? It works fine for me, settings/security/smart lock/face unlock opens and I can set it up.
_mysiak_ said:
When does it crash? It works fine for me, settings/security/smart lock/face unlock opens and I can set it up.
Click to expand...
Click to collapse
I can tap on the trusted face icon and then pressing 'Set up', and then once I press 'Next' it force closes... "Trusted Face has stopped"
Roykooiman said:
I can tap on the trusted face icon and then pressing 'Set up', and then once I press 'Next' it force closes... "Trusted Face has stopped"
Click to expand...
Click to collapse
As you mentioned that you tried to replace the app, I'd suggest:
1. clear facelok app cache and data
2. make sure that it has Camera permission enabled
3. make sure it's not disabled
_mysiak_ said:
As you mentioned that you tried to replace the app, I'd suggest:
1. clear facelok app cache and data
2. make sure that it has Camera permission enabled
3. make sure it's not disabled
Click to expand...
Click to collapse
1 tried that a few times already...
2 It has
3 it is enabled
also setproperties to: rw-r-r
It download the update, But everytime it tries to install it says "Installation Problem". And if I click "try again" It Download the update again. Tried it 3 times but everytimes it fails to update.
I haven't rooted my device or haven't unlocked bootloader
Didn't done any custom modifications at all.
No Gcam, No Magisk. Nothing.....
It's so frustrating & annoying. Please give a solution to this.
[ XDA didn't let me post images ]
Update : I also created a mi community thread and many other users are facing this same issue.
Take to service centre
.:Addicted:. said:
Take to service centre
Click to expand...
Click to collapse
Any other ways???
Download April fastboot ROM then flash via mi flash tool then choose flash all except storage
DevXp.Rahul said:
Any other ways???
Click to expand...
Click to collapse
Si you never rooted it ? Never did something out of stock ?
Install magisk app and trigger the safetynet test
See if it passes it especially the basic integrity which stands for system modification
Else you can unlock bootloader
Do the trick to not wipe data (I do not guaranty it will work for you)
Flash firmware with fastboot (be careful the script inside firmware have unlock/relock bootloader remove them before continue
Have You enabled Camera2api ?
ant19 said:
Have You enabled Camera2api ?
Click to expand...
Click to collapse
Nope. As I said haven't done any modifications to my phone.
Since you haven't done anything from your side, it would be best if you give it to service centre.
Or you can read tutorial about flashing fastboot images.
Since its your 3rd post, i assume you never had flashing experience. Best would be taking it to service centre
.:Addicted:. said:
Since you haven't done anything from your side, it would be best if you give it to service centre.
Or you can read tutorial about flashing fastboot images.
Since its your 3rd post, i assume you never had flashing experience. Best would be taking it to service centre
Click to expand...
Click to collapse
Thank you for suggestion Lemme try calling the service centre first. If they didn't resolve the issue I will definitely try flashing it via fastboot mode.
You should try erasing the Google Services Framework data. It would help.
A fair warning about messing up Google Services Framework:
https://c.mi.com/thread-821007-1-0.html
Please share your fpcalibrationresult file for comparison.
My fingerprint reader is not working - if you have any hints how to get it working please let me know.
When I run Engineeringmode (+#808#) -> Device Debugging -> Fingerprint Test -> Fingerprint Optical calibration -> 6776 -> Start -> Next
I get the error:
0x60 SPI Test Timeout
257_timout: wait for cmd[223:Get Sensor ID-20000 ms]
which does not make sense to me as the fpcalibration shows G6_7
and aquire fingerprint chip information also shows
G_OPTICAL_G6_7.0...
my fpcalibrationresult file:
Calibration time:2020-09-16-04_29_54
Calibration icon color: Green
SPI_TEST: PASS: SMT1_ID:1,SMT2_ID:1,FLASH ID:0,SENSOR ID:0,MCU ID:0,SENSOR VERSION:0,SENSOR INFO:G6_7
SPI_RST_INT_TEST: OTP TEST PASS
MT_CHECK_TEST: PASS
FT_EXPO_AUTO_CALIBRATION_TEST: CHIPID:0x5131335239372e01877b802af9b200000000,
PASS
INIT_TEST: OPERATION_STEP_CALCULATE_GAIN_TWO_LIGHT_MEAN TEST PASS
CAPTURE_H_FLESH_TEST: OPERATION_STEP_BASEDATA_MAX_COLLECT TEST PASS
CAPTURE_M_FLESH_TEST: OPERATION_STEP_BASEDATA_MID_COLLECT TEST PASS
CAPTURE_L_FLESH_TEST: OPERATION_STEP_BASEDATA_MIN_COLLECT TEST PASS
CAPTURE_H_DARK_TEST: OPERATION_STEP_BASEDATA_MAX_DARK_COLLECT TEST PASS
CAPTURE_M_DARK_TEST: OPERATION_STEP_BASEDATA_MID_DARK_COLLECT TEST PASS
CAPTURE_L_DARK_TEST: OPERATION_STEP_BASEDATA_MIN_DARK_COLLECT TEST PASS
CAPTURE_DARK_BASE_TEST: OPERATION_STEP_BASEDATA_DARK_COLLECT TEST PASS
CAPTURE_CIRCLE_DATA_TEST: OPERATION_STEP_CIRCLEDATA_COLLECT TEST PASS
CAPTURE_FLASH_CIRCLEDATA_TEST: OPERATION_STEP_CIRCLE_CHARTDATA_COLLECT TEST PASS
CAPTURE_CHECKBOX_TEST: OPERATION_STEP_CHARTDATA_COLLECT TEST PASS
CAPTURE_CHART_TEST: OPERATION_STEP_GET_KB_CALIBRATION TEST PASS
SENSOR_VENDOR: OPERATION_STEP_CALCULATE_SIMPLIFIED_PERFORMANCE_INDICATORS TEST
MINDIFFFLESHHM:472,MINDIFFFLESHHM_MIN:200,MINDIFFFLESHHM_RESULTASS,(>=200)
MINDIFFFLESHML:472,MINDIFFFLESHML_MIN:100,MINDIFFFLESHML_RESULTASS,(>=100)
MINDIFFBLACKHM:269,MINDIFFBLACKHM_MIN:100,MINDIFFBLACKHM_RESULTASS,(>=100)
MINDIFFBLACKML:273,MINDIFFBLACKML_MIN:50,MINDIFFBLACKML_RESULTASS,(>=50)
MAXLIGHTSTABILITY:11.39,MAXLIGHTSTABILITY_MAX:20.00,MAXLIGHTSTABILITY_RESULTASS,(<20.00)
BADPIXELNUM:1,BADPIXELNUM_MAX:150,BADPIXELNUM_RESULTASS,(<=150)
BADBLOCKNUM:0,BADBLOCKNUM_MAX:10,BADBLOCKNUM_RESULTASS,(<=10)
BADPIXELALLBLOCKS:0,BADPIXELALLBLOCKS_MAX:87,BADPIXELALLBLOCKS_RESULTASS,(<=87)
BADLINENUM:0,BADLINENUM_MAX:0,BADLINENUM_RESULTASS,(<=0)
BADBLOCKLARGEST:0,BADBLOCKLARGEST_MAX:67,BADBLOCKLARGEST_RESULTASS,(<=67)
HOTPIXELNUM:1,HOTPIXELNUM_MAX:100,HOTPIXELNUM_RESULTASS,(<=100)
HOTBLOCKLARGEST:1,HOTBLOCKLARGEST_MAX:17,HOTBLOCKLARGEST_RESULTASS,(<=17)
HOTLINENUM:0,HOTLINENUM_MAX:0,HOTLINENUM_RESULTASS,(<=0)
DPAADIFFDARK:3,DPAADIFFDARK_MAX:22,DPAADIFFDARK_RESULTASS,(<=22)
DPBADPIXELNUM:0,DPBADPIXELNUM_MAX:50,DPBADPIXELNUM_RESULTASS,(<=50)
DPBADPIXELINROW:0,DPBADPIXELINROW_MAX:8,DPBADPIXELINROW_RESULTASS,(<=8)
DPSNOISEDARKN:0.43,DPSNOISEDARKN_MAX:5.10,DPSNOISEDARKN_RESULTASS,(<=5.10)
ANTIFAKEDX:15.04,ANTIFAKEDX_MIN:6,ANTIFAKEDX_MAX:30,ANTIFAKEDX_RESULTASS,(6<=x<=30)
ANTIFAKEDY:14.07,ANTIFAKEDY_MIN:6,ANTIFAKEDY_MAX:30,ANTIFAKEDY_RESULTASS,(6<=x<=30)
LIGHTHIGHMEAN:2243,LIGHTHIGHMEAN_MIN:1000,LIGHTHIGHMEAN_MAX:3000,LIGHTHIGHMEAN_RESULTASS,(1000<=x<=3000)
TNOISEDARKN:0.27,TNOISEDARKN_MAX:1.50,TNOISEDARKN_RESULTASS,(<=1.50)
TNOISELIGHTN:7.47,TNOISELIGHTN_MAX:20.00,TNOISELIGHTN_RESULTASS,(<=20.00)
SNOISEDARKN:0.22,SNOISEDARKN_MAX:1.60,SNOISEDARKN_RESULTASS,(<=1.60)
TNOISELIGHTN:40.90,TNOISELIGHTN_MAX:120,TNOISELIGHTN_RESULTASS,(<=120)
SNOISEFLATL:2.81,SNOISEFLATL_MAX:5,SNOISEFLATL_RESULTASS,(<=5)
SIGNALLLOW:52.23,SIGNALLLOW_MIN:31.56,SIGNALLLOW_RESULTASS,(>=31.56)
SIGNALLHIGH:97.26,SIGNALLHIGH_MIN:53.04,SIGNALLHIGH_RESULTASS,(>=53.04)
TSNRLOW:14.383,TSNRLOW_MIN:12.000,TSNRLOW_RESULTASS,(>=12.000)
TSNRHIGH:27.043,TSNRHIGH_MIN:20.580,TSNRHIGH_RESULTASS,(>=20.580)
DIFFBLACKLD:566,DIFFBLACKLD_MIN:50,TSNRHIGH_RESULTASS,(>=50)
ASSEMBLYXOFFSET:1.47,ASSEMBLYXOFFSET_MAX:12.00,ASSEMBLYXOFFSET_RESULTASS,(<=12.00)
ASSEMBLYYOFFSET:0.78,ASSEMBLYYOFFSET_MAX:12.00,ASSEMBLYYOFFSET_RESULTASS,(<=12.00)
ASSEMBLYANGELOFFSET:0.25,ASSEMBLYANGELOFFSET_MAX:2.50,ASSEMBLYANGELOFFSET_RESULTASS,(x<=2.50)
POLARDEGREE:1.68, POLARDEGREE_MIN:1.35, POLARDEGREE_RESULTASS,(>=1.35)
LIGHTLEAKDARK:3,LIGHTLEAKDARK_MAX:30,LIGHTLEAKDARK_RESULTASS,(<=30)
LIGHTLEAKRATIO:0.57,LIGHTLEAKRATIO_MAX:0.75,LIGHTLEAKRATIO_RESULTASS,(<=0.75)
DIFFOFFSET:472,DIFFOFFSET_MAX:1500,DIFFOFFSET_RESULTASS,(<=1500)
VALIDAREARATIO:1.00,VALIDAREARATIO_MIN:0.80,VALIDAREARATIO_RESULTASS,(>=0.80)
CHARTDIRECTION:1,CHARTDIRECTION_MIN:15,CHARTDIRECTION_MAX:15,CHARTDIRECTION_RESULTASS,()
PASS
Did this happen after you upgraded to OOS 13 possibly, or are you running a custom ROM? I went from a custom ROM to OOS 13 just to try it out, but I didn't use MSM to do it so my fingerprint didn't work either until I did a local update of the same OOS 13 ROM and it fixed my fingerprint scanner KB2005 8T otherwise if you made a backup of your persist partition you can Flash that and that usually fixes it
parag0n1986 said:
Did this happen after you upgraded to OOS 13 possibly, or are you running a custom ROM? I went from a custom ROM to OOS 13 just to try it out, but I didn't use MSM to do it so my fingerprint didn't work either until I did a local update of the same OOS 13 ROM and it fixed my fingerprint scanner KB2005 8T otherwise if you made a backup of your persist partition you can Flash that and that usually fixes it
Click to expand...
Click to collapse
I just got an OTA Update like 2h ago and now it is working again. Need to reroot though.
excogitation said:
I just got an OTA Update like 2h ago and now it is working again. Need to reroot though.
Click to expand...
Click to collapse
Ok, glad to hear you got it working. Need help with root?
parag0n1986 said:
Ok, glad to hear you got it working. Need help with root?
Click to expand...
Click to collapse
I'm used to rerooting with TWRP that is actually not working for the 8t Android 12 for now - so yes - if you have a good way to do it please share.
My current thoughts: get the original update zip file (seems to not yet be available easily),
extract boot partition, patch with magisk, flash in fastboot.
excogitation said:
I just got an OTA Update like 2h ago and now it is working again. Need to reroot though.
Click to expand...
Click to collapse
Ok, glad to hear you got it working. Need help with root
excogitation said:
I'm used to rerooting with TWRP that is actually not working for the 8t Android 12 for now - so yes - if you have a good way to do it please share.
My current thoughts: get the original update zip file (seems to not yet be available easily),
extract boot partition, patch with magisk, flash in fastboot.
Click to expand...
Click to collapse
Exactly how. I have the boot image if needed?
parag0n1986 said:
Ok, glad to hear you got it working. Need help with root
Exactly how. I have the boot image if needed?
Click to expand...
Click to collapse
KB2003_11.C.36_boot.img
Hey guys, my fingerprint sensor is also dead after upgrading to OOS13. No animation, no vibration. Engineeringmode (*#899#) fingerprint autotest says PASS. Upgradeded from OOS11 ota via OOS12 and Oxygen Updater local Upgrade. Keep root by Magisk install after OTA. Any ideas how to fix that?
I have found the solution. UNSF 2.2.1 Magisk module update to 2.3.1 and it works again.
Thanks to the hint https://forum.xda-developers.com/t/solved-debugging-fingerprint-reader-not-working.4493281/
Hi, my fingerprint doesn't work... kb2003 version. I can't run the engenering test because I got SPI error: Your phone is locked
Could someone share the persist.img with me? I don't want to exchange the whole partition I just want to compare some file on it. Thnx
One idea is to wait until Android 13 (and Android 12 for that matter) actually works.
Both A12 and A13 are buggy nonsense with bad battery. And I will not be "upgrading" unless there is no other option.
This whole MUST HAVE LATEST VERSION fetish is becoming a little tiresome.
gcsuri said:
Hi, my fingerprint doesn't work... kb2003 version. I can't run the engenering test because I got SPI error: Your phone is locked
Could someone share the persist.img with me? I don't want to exchange the whole partition I just want to compare some file on it. Thnx
Click to expand...
Click to collapse
Hi,
Did you manage to solve your fingerprint issue?
333robbie333 said:
Hi,
Did you manage to solve your fingerprint issue?
Click to expand...
Click to collapse
yes. The problem was the incorrect persist partition.The official service couldn't repait the partition, so they replace the mainboard.
Take care of the persist partition.
gcsuri said:
yes. The problem was the incorrect persist partition.The official service couldn't repait the partition, so they replace the mainboard.
Take care of the persist partition.
Click to expand...
Click to collapse
Thanks a lot! Now I'm scared to install a custom ROM on my device lol
333robbie333 said:
Thanks a lot! Now I'm scared to install a custom ROM on my device lol
Click to expand...
Click to collapse
Just make a backup of you persist partition first just in case. I always do.
parag0n1986 said:
Just make a backup of you persist partition first just in case. I always do.
Click to expand...
Click to collapse
Please share it for me, help me.