[solved] fpcalibrationresult needed (fingerprint scanner not working) - OnePlus 8T Guides, News, & Discussion

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.

Related

XNPH33R OTA with modified Updater-Script

https://www.mediafire.com/?922rx2xn53yt72r
Here it is. Enjoy. And yes it works on mine :fingers-crossed:
It's a new Official Update
Changelog taken from Android Police
-A new radio image.
-Touchscreen fixes (addresses BACON-55, which was originally reported and subsequently brought to our attention by Ausdroid). There's also an extensive thread on OnePlus' forums about it, among many other places (forum account needed).
Update: The fix is not complete, as reports of jumpiness are surfacing once again. It did fix the deadzone / random touches issue which prevented me from unlocking my phone for 10-15s at a time as I simply couldn't trace my pattern due to all the jumping around.
Unfortunately, the grounding issue which results in multitouch going nuts remains unfixed and must be resolved via another driver update. Another excruciating wait begins.
-Decreased power consumption in idle state (fixes BACON-599 which we wrote about here).
-Unspecified audio fixes.
-CVE-2014-4943 and another unspecified security update.
MD5 : 7538A068384C52FF6CA06C4B128B5ED1
P/S : I didn't have that jumpiness of sort, mine is working fine.
Flashing this worked perfectly for me. Thanks.
Glad to see it worked
Good job, works great
ravearamashi said:
https://www.mediafire.com/?922rx2xn53yt72r
Here it is. Enjoy. And yes it works on mine :fingers-crossed:
MD5 : 7538A068384C52FF6CA06C4B128B5ED1
Click to expand...
Click to collapse
Awesome!!!! Thanks so much
what is modified updater-script, is this the ota which is pushed by oneplus?
Is there a change log anywhere?
Fist and foremost,THANKS !
Could you perhaps elaborate on the update a bit ? e.g. this the official NEW update ?
boomam said:
Is there a change log anywhere?
Click to expand...
Click to collapse
You can check it out here. http://www.androidpolice.com/2014/0...ed-fixes-here-is-the-zip-for-manual-flashing/
Seems to work fine, thanks
Thanks m8, works perfectly.
What does it mean by modified updater script?
nice
Thank you
surronix said:
What does it mean by modified updater script?
Click to expand...
Click to collapse
I'm wondering the same thing. Can I flash this if I am on CM nightlies?
GETCASHMONEY said:
I'm wondering the same thing. Can I flash this if I am on CM nightlies?
Click to expand...
Click to collapse
No, it's strictly for CM11S
See, back when XNPH30O came out, lot of people couldn't update using OTA method when they are rooted/running Xposed/custom kernel and so forth because the OTA update would check the files before updating begins which of course the update would fail on devices running the aforementioned stuff. And a guy named Ludester modified the updater-script to bypass that file check and of course the update worked on these modified devices. So fast forward to this update, I just did the same thing.
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
joeee89 said:
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
Click to expand...
Click to collapse
Yes, and wipe cache after flashing then reboot.
joeee89 said:
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
Click to expand...
Click to collapse
Yes you can
wipe
there is no need to wipe
i just installed it an no problems
i didt no wipe
Nope.
Phone is stuck at the OnePlus Logo after flashing via TWRP. Wiping caches and re-flashing didnĀ“t help.

BND-L24 Unbrick And restore Honor 7x USA

Ok guys bare with me. This is my first Thread. So it may look a little different then the others :laugh:
At least Your honor 7x will no longer be a paper weight
I posted last week that I do Indeed have a good TWRP Honor 7x BND-L24 USA Variant. Since then I have been getting hammered with requests for it. So being the great guy that I am, I have come to the rescue. NO MORE PAPER WEIGHT :laugh: I have also included TWRP 3.1.1. You will Find Direct download links below.
I have heard that Huawei will be releasing the firmware by end of next week. Go to play store and download Huawei Firmware
Finder(FF) To keep checking for it. Once there you can download it through Huawei FF.
When I did the backup TWRP gave me error 255 with the data.img but it did still back it up. I have the boot.img, system.img and data.img. data.img (data.img untested but should work)
If it does not I have a post here https://forum.xda-developers.com/showthread.php?p=75735265#post75735265 that explains how to use just the boot.img and system.img to recover your phone. IGNORE that it is for the 6x. It does indeed work with the 7x
If your phone is bricked and do not have twrp
1.Turn off phone
2. hold volume down while plugging in usb cable from your pc or laptop. That will put you in fastboot.
Tutorial here https://www.xda-developers.com/how-to-root-honor-7x/ on how to download and install ADB tools.
3.. Download TWRP 3.1.1 for honor 7x here https://drive.google.com/open?id=1dzP5ie7vQEn_dGfZHI383bt2sFxwtcTb
For people with TWRP installed
1. Download My TWRP backup here https://drive.google.com/open?id=1Udc4thELESZ4n_nXYmx6loQtTkjHOqSy
2. Extract the zip file to your ext, sdcard.
3. Boot phone into twrp.(Bricked phones hold volume up and press power to launch twrp assuming it is installed.
4. Select restore in twrp menu then choose sd card then the backup folder.
5. Flash the boot system and data img files
6 Reboot.
NO more paper weight :good:
Oh if anyone has twrp 3.2x that works with this with 7x BND-L24 do share please
Well hope this was not to bad :laugh:
Hit that thanks button. Yea that one under my post on the right :laugh:
Hope this has helped
Thank you
lowspeed said:
Thank you
Click to expand...
Click to collapse
No problem. Least I can do. This site has helped me out a lot
Paper weights suck :laugh:
Didn't work. I got to the "booting now" screen and was stuck there forever. I had to restore my old System and Boot partitions to get back to normal.
Didn't Work for me. goes tot the erecovery page.
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
tomjfmu said:
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
Click to expand...
Click to collapse
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
dukethedj said:
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
Click to expand...
Click to collapse
Yes please would love some insight on this. thanks in advance.
forgotenxlegacyx said:
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Click to expand...
Click to collapse
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
Would you mind linking a thread on how that is done? sorry for my ignorance
forgotenxlegacyx said:
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
Click to expand...
Click to collapse
i have an idea, maybe you can make a backup not just including the system, data, and boot but other stuff. Because I accidentally wiped everything, and I changed the vender to a10/tl10, and that bricked the phone even more. And the data img doesn't work. You can fix it with this https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468. If someone has a working bnd-l24 or bnd-l34 can you give me everything in the backup?
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
So you first do that then you do the rest?
Tried again. Getting the 255 error when flashing the Data
Yeah, error 255 is boot looping me too.
does it works well?
Thanks!
RoxRedEye said:
Thanks!
Click to expand...
Click to collapse
You were able to get it to work?
I want to get behind and support this, so much, .But the OP is not registered user, so cant even verify their reputation.
I am late to this device and thread, but my phone will arrive tmw.
I would like to know if this is the only current available restore method for BND-L24?

Bootloop without reason!! Any solution except Factory Reset?

Hi everyone, I owns a Black, Made in China variant Mi A1, bought it almost 10 months ago so it's in brand new condition.
A night I was using it as regular, watching YouTube, It suddenly restarted automatically, and stuck on 'Android One' boot animation.
I wasn't doing any heavy or intensive task, was not having any issue except storage full. The device is on official stock rom and on June security patch with Android 8.1.
I've tried >?1. Apply update from ADB in recovery mode with June update, which gave me -> E: footer is wrong. E: signature verification failed. Installation aborted
>?2. Apply update from SD card with the same update as above, which gave me -> Couldn't mount SD card
Bootloader is locked, USB debugging is off, no custom recovery installed.
Is there any way to make it work again without erasing user data? I'm familiar with all kinds of Command Line Interface and with almost every tech term. Any help would be appreciated.?
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
Hi,
i have also experienced the same issue recently and struggling hard to make it working again.
I have tried with MI flash but u need to have a bootloader unlocked as well. If not, flashing will not start.
Shashankjindal said:
Hi everyone, I owns a Black, Made in China variant Mi A1, bought it almost 10 months ago so it's in brand new condition.
A night I was using it as regular, watching YouTube, It suddenly restarted automatically, and stuck on 'Android One' boot animation.
I wasn't doing any heavy or intensive task, was not having any issue except storage full. The device is on official stock rom and on June security patch with Android 8.1.
I've tried >1. Apply update from ADB in recovery mode with June update, which gave me -> E: footer is wrong. E: signature verification failed. Installation aborted
>2. Apply update from SD card with the same update as above, which gave me -> Couldn't mount SD card
Bootloader is locked, USB debugging is off, no custom recovery installed.
Is there any way to make it work again without erasing user data? I'm familiar with all kinds of Command Line Interface and with almost every tech term. Any help would be appreciated.
Click to expand...
Click to collapse
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
Does it work in locked bootloader? Btw thanks for the reply.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
Can you describe what in the data partition caused this? Because I've been using this device with 90% storage filled for months??*.
And I've factory reset the device as there was no other ways to make it work again but still I want to know what was the cause of the problem.
Shashankjindal said:
Can you describe what in the data partition caused this? Because I've been using this device with 90% storage filled for months??*.
And I've factory reset the device as there was no other ways to make it work again but still I want to know what was the cause of the problem.
Click to expand...
Click to collapse
When memory is almost full R/W errors can occur.
Maybe 90% you see is not including temporary-swap files, so that you are dangerously close to 100% storage filled.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
sipollo said:
When memory is almost full R/W errors can occur.
Maybe 90% you see is not including temporary-swap files, so that you are dangerously close to 100% storage filled.
Click to expand...
Click to collapse
Thank you for your answer & time, I'll be carefull in the future.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
I have just softbricked my Mi A1 and need to flash the official rom with MiFlash, problem is that I can't find the right file to flash. Any tips to where I can download the official firmware? I'm looking for the zipped version, not an image. MiFlash can't read the images I've downloaded so far.
FantLarve said:
I have just softbricked my Mi A1 and need to flash the official rom with MiFlash, problem is that I can't find the right file to flash. Any tips to where I can download the official firmware? I'm looking for the zipped version, not an image. MiFlash can't read the images I've downloaded so far.
Click to expand...
Click to collapse
Here are some of the links where you can find the official rom in .zip format. Check if they are compatible with MiFlash tool-
https://firmwarefile.com/xiaomi-mi-a1
https://dhananjaytech.com/flash-stock-rom-mi-a1-through-twrp/
Here is the XDA thread- https://forum.xda-developers.com/mi-a1/development/rom-tissot-stock-oreo-8-0-rooted-t3735760.
I'll be happy if this was helpful.
Shashankjindal said:
Here are some of the links where you can find the official rom in .zip format. Check if they are compatible with MiFlash tool-
https://firmwarefile.com/xiaomi-mi-a1
https://dhananjaytech.com/flash-stock-rom-mi-a1-through-twrp/
Here is the XDA thread- https://forum.xda-developers.com/mi-a1/development/rom-tissot-stock-oreo-8-0-rooted-t3735760.
I'll be happy if this was helpful.
Click to expand...
Click to collapse
Great stuff thanks.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
There was another thread where someone proceeded to soft brick his device after downloading a file despite having low available storage.
barrack1 said:
There was another thread where someone proceeded to soft brick his device after downloading a file despite having low available storage.
Click to expand...
Click to collapse
Thank you for the help, there seems just no way to save user data, factory reset is the only option.
Shashankjindal said:
Does it work in locked bootloader? Btw thanks for the reply.
Click to expand...
Click to collapse
works

SOLVED:Stuck at PIN input, then reboots

Well, I f*cked up.
Fastboot works, I can flash stock rom via Xiaomi Flash. Flashing completes without any problems. A notification about encypting phone shows up, at 3% it jumps to 100% and resumes boot. Now after each boot, phone freezes at "input your sim pin" and reboots. Over and over again. What can I try, please help :
edited
twister26 said:
There is an reward for whoever helps me solve this issue
Click to expand...
Click to collapse
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
dfranco51207 said:
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
Click to expand...
Click to collapse
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
twister26 said:
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
Click to expand...
Click to collapse
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Let me guess. From Pie to Oreo or Nougat?
Mercoory said:
Let me guess. From Pie to Oreo or Nougat?
Click to expand...
Click to collapse
yes, exactly is there a thread already open somewhere here and i missed? last time TWRP was working, I even got a message "your system has been destroyed" or something like that.
sipollo said:
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Click to expand...
Click to collapse
will try!
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
ccalixtro said:
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
will give it a read, it it works, I'll PM you and you'll give me your paypal address. Fair is fair.
can't unlock OEM, because I can't boot up to developer tools. great, just great. will try to fix that first.
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
fdc77 said:
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
Click to expand...
Click to collapse
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
twister26 said:
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
Click to expand...
Click to collapse
i had a problem like yours, but i have flashed stock rom in non EDL mode and everything had start to work apart LTE band missing that i restored with qualcomm's tools
which stock rom have you try to flash? are you downgrading from oreo? bootloop on android one logo after downgrading is a common issue due to ARB (anti rollback protection)
twister26 said:
Whoever saves my precious Mi A1 gets 10$ on his paypal.
Click to expand...
Click to collapse
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
tropbel said:
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
Click to expand...
Click to collapse
reward is cancelled from this point on i will reward the one who helped me so far tho. still working on solving the problem so winner has not been decided yet.
you don't understand.
There are no winners and no loosers.
You are free to donate to anyone you want, but your post boost and encourages a bad attitude.
If people start to solve only paid problems, the spirit of the community will be destroyed.
The problem is with the Pie specific partition table
I write the whole guide from memory, so it can differ a bit.... I skipped some steps ( erasing, reboot, fastboot mode, TWRP loading via fastboot, OEM unlock )
From previous writings I think you can know the skipped steps.
Keep in mind: It is dangerous, you can loose your IMEI ( it will only work again with Pie - or there are some writings at forum how can you manually change it. ).
Steps:
1 - Backup with TWRP (fastboot) efs,persist,modem & make copy to your computer and or to your cloud provider.
2 - Create a new folder in Internal Storage -> TWRP -> BACKUP -> With a new date directory ( the backup already made one, make a new folder, with different date )
3 - Download someone's older TWRP backup from xda (I cheated, I copied the following links ) :
(I'm still a new user, so can't directly write url's )
Mediafire : https COLON SLASH SLASH bit.ly SLASH 2QU5NtC
Mirror: Google Drive : https COLON SLASH SLASH bit.ly SLASH 2UN1DTo
4 - Unpack, and copy EFS to the folder created 2 point
5 - Fastboot TWRP -> Restore EFS
6 - Flash the Official latest firmware from en.miui.com ( If you want to make sure go with EDL mode )
7 - Now, the IMEI & Mac addresses are missing. Don't panic! Download update with System Updates.
8 - When you are on Pie again, restore your first TWRP (fastboot) persist partition
9 - One more System restore
At this time, you will have IMEI & Mac addressees, and hopefully a working phone.
Hope this helps. The same thing happened with me 2 weeks ago. This is how I solves it.
Thank you, I solved it yesterday. Hopefully this post will come in handy for other people!

find device storage corrupted your device is unsafe now

hey guys i recently flashed pixel experience on my redmi k20 but i decided to revert back to stock so i flashed latest stable version through mi flash but now i am getting "find device storage corrupted your device is unsafe now" notifications did i messed something up? and i had an unlocked bootloader but now i cant unlock it. the error i get is "you should wait until 30 days before you can unlock another device"
once you've unlocked the bootloader, you can unlock it anytime again and as often as you want. have tested this several times, just once again with the same mi account unblock - without waiting.
how did you leave MIUI installed with MIflash and lock down on the bottom right?
You somehow corrupted your persist partition. When you are able to unlock again, you can fix that by flashing persist.img from fastboot image to persist partition via TWRP. You can't flash that via fastboot, that will not work. Be aware that you will loose Widevine L1 forever on MIUI (should still work on custom roms) unless you have a backup of your persist partition you can restore.
lucifer said:
hey guys i recently flashed pixel experience on my redmi k20 but i decided to revert back to stock so i flashed latest stable version through mi flash but now i am getting "find device storage corrupted your device is unsafe now" notifications did i messed something up? and i had an unlocked bootloader but now i cant unlock it. the error i get is "you should wait until 30 days before you can unlock another device"
Click to expand...
Click to collapse
Why did you leave the pixel experience ROM , wasn't it good . Just wanted to know because I want to flash it too
nill3bor said:
once you've unlocked the bootloader, you can unlock it anytime again and as often as you want. have tested this several times, just once again with the same mi account unblock - without waiting.
how did you leave MIUI installed with MIflash and lock down on the bottom right?
Click to expand...
Click to collapse
yup locked with mi flash with the lock option on bottom but can't unlock it again with the same id somehow now the phone is seen as new device
nckmml said:
You somehow corrupted your persist partition. When you are able to unlock again, you can fix that by flashing persist.img from fastboot image to persist partition via TWRP. You can't flash that via fastboot, that will not work. Be aware that you will loose Widevine L1 forever on MIUI (should still work on custom roms) unless you have a backup of your persist partition you can restore.
Click to expand...
Click to collapse
can service center fix that for me.?
Benfatica said:
Why did you leave the pixel experience ROM , wasn't it good . Just wanted to know because I want to flash it too
Click to expand...
Click to collapse
no its works great my poco f1 screen broke thats why i reverted back to miui on k20
lucifer said:
yup locked with mi flash with the lock option on bottom but can't unlock it again with the same id somehow now the phone is seen as new device
Click to expand...
Click to collapse
its not good?
but you have not created a backup of twrp?
but you can create a new account, because it's 7 days to unlock. but you can only unlock a phone every 30 days!
what did you do, why is the partition corrupt? that should not happen with the image!
nill3bor said:
its not good?
but you have not created a backup of twrp?
but you can create a new account, because it's 7 days to unlock. but you can only unlock a phone every 30 days!
Click to expand...
Click to collapse
no its not good
yes i created a backup but to flash twrp again i need unlocked bootloader
will try with new account
and can servce center fix this for me.?
And i just flashed with mi flash tool nothing else it works fine on my poco done several times already but somehow something went wrong
lucifer said:
no its not good
yes i created a backup but to flash twrp again i need unlocked bootloader
will try with new account
and can servce center fix this for me.?
Click to expand...
Click to collapse
create a new account, wait and after unlock flash the backup and report
MIUI works good or do you have problem? IMEI and MAC its ok?
nill3bor said:
create a new account, wait and after unlock flash the backup and report
MIUI works good or do you have problem? IMEI and MAC its ok?
Click to expand...
Click to collapse
Miui works fine except it can't sync with mi cloud
Imei and mac is fine
update : mi cloud sync works on new id
lucifer said:
Miui works fine except it can't sync with mi cloud
Imei and mac is fine
update : mi cloud sync works on new id
Click to expand...
Click to collapse
wait for unlock, flash partion here or flash a backup (partition)
Flash twrp persist.img
nill3bor said:
wait for unlock, flash partion here or flash a backup (partition)
Click to expand...
Click to collapse
Ok will wait for unlock and will update
Thanks for the help
Those that haven't flashed their persist partition and are rooted, are you able to look in there and see if there's any files or folders related to the widevine certification?
nill3bor said:
wait for unlock, flash partion here or flash a backup (partition)
Click to expand...
Click to collapse
If i flash partion that is not my backup will i lose widewine L1 on miui.?
lucifer said:
If i flash partion that is not my backup will i lose widewine L1 on miui.?
Click to expand...
Click to collapse
That's why I asked about IMEI, Bluetooth and sensors. But before you flash, try this one again and report.
Of course, twrp must be installed.
did you create a new account?
do you have less than 30 days wait now?
did you have a foreign backup fash before?
is the IMEI the same number as on the packaging?
nill3bor said:
That's why I asked about IMEI, Bluetooth and sensors. But before you flash, try this one again and report.
Of course, twrp must be installed.
did you create a new account?
do you have less than 30 days wait now?
did you have a foreign backup fash before?
is the IMEI the same number as on the packaging?
Click to expand...
Click to collapse
yes every sensor is working fine
yes i did create a new account
7 days wait now
what is foreign backup?
yes imei is same as on packaging
and can service center fix this for me.?
lucifer said:
yes every sensor is working fine
yes i did create a new account
7 days wait now
what is foreign backup?
yes imei is same as on packaging
and can service center fix this for me.?
Click to expand...
Click to collapse
thats ok, try this
if you do not have your own backup, I would not import it, because in the persist.img sensedata IMEI bluetooth etc stored in the partition
you just have to wait, then you try what was advised and report
nill3bor said:
thats ok, try this
if you do not have your own backup, I would not import it, because in the persist.img sensedata IMEI bluetooth etc stored in the partition
you just have to wait, then you try what was advised and report
Click to expand...
Click to collapse
ok i will wait try and report but will service center be able to solve this problem.?

Categories

Resources