Related
YESSSSSS A NEW FP THREAT AGAIN YOUR FP IS NOT..... I REPEAT NOT DEAD. I KNEW IT... I'm almost sure it's the bootloader. Notice the attached picture s
Why. Mine died also after flashing about a month ago. Shortly after my new X2 arrived.
It does not die couse of heating issues because I heated my X2 to disassemble it. And that heating is way mutch hotter than charging does.
What I did.
Rooted. Flashed TRWP 3.0.2.0 (not higher) flashed pure nexus on it. And FP got bricked. On top of pure nexus I flashed 26s Rom. This bricks the X2 cause it hangs in bootloop of course. Now you're only able to use the unbrick method. When you do that. Flash the given QFill developers Rom. When you flashed that one and booted up first go to settings/storage and do a factory whipe tikking erase internal storage also. Perform the factory reset. Reboot and set-up fast again. Activate developers mode again. And again reflash by using fastboot mode TRWP so you get the TRWP recovery mode. After that flash Pure nexus again. All should be fine now. Recalibrate your fp several times And it works
As you can see under leeco extras. The font does not match up my system font. This type of font (Hindy I guess) is also seen under under security settings. FingerPrint callibration...
I'm almost positive that it's the bootloader. Not 100% sure.
Succes
That's exactly what I did last Wednesday. I flashed the developers ROM, then flashed TWRP without setting anything up, and flashed another ROM. My fp sensor remained dead, as it is right now. I'm glad to hear that you managed to recover it using this method, but it didn't work for many of us, me included.
Anyway, thanks for sharing. This may work for a lot of people, and everyone with a dead fingerprint sensor should try it. It's not risk free, but it's not so hard to do, either.
Mine was dead after one week, why so much hassle? it should work out of the box or stay dead as it is. It's the hardware problem on Le max 2.
I got LE Pro 3 too, it work 100% from day one until now, no issue.
Moon75 said:
Mine was dead after one week, why so much hassle? it should work out of the box or stay dead as it is. It's the hardware problem on Le max 2.
I got LE Pro 3 too, it work 100% from day one until now, no issue.
Click to expand...
Click to collapse
Well, if you don't care about getting a replacement or a refund, why not try to recover the sensor yourself, by every means possible? You're also free to leave as it is. I'm now using an app that unlocks the screen using the proximity sensor, along with face recognition unlock (thanks to Small EUI ROM) so I don't care too much about the dead fp sensor now, but I have not completely given up on it. If someone finds an easy and reliable way to fix it, I may try it.
Hi, for sure if there is easy fix I will fix it but there is none and many people have dead FP on this phone because they can't fix it. For Nougat rom you can wake it up with Volume button but stock rom you can't. There is some app you can install and wake up the phone by double tab or cover sensor as you mentioned. If FP working sure it's better but don't have it not big deal.
Moon75 said:
Mine was dead after one week, why so much hassle? it should work out of the box or stay dead as it is. It's the hardware problem on Le max 2.
I got LE Pro 3 too, it work 100% from day one until now, no issue.
Click to expand...
Click to collapse
Mine worked perfectly untill I flashed let max 2 day after arrival. It has something to do with the bootloader. Because I got the 26s version bootloader in it and now it works while using pure nexus droid
jman0 said:
That's exactly what I did last Wednesday. I flashed the developers ROM, then flashed TWRP without setting anything up, and flashed another ROM. My fp sensor remained dead, as it is right now. I'm glad to hear that you managed to recover it using this method, but it didn't work for many of us, me included.
Anyway, thanks for sharing. This may work for a lot of people, and everyone with a dead fingerprint sensor should try it. It's not risk free, but it's not so hard to do, either.
Click to expand...
Click to collapse
And you did use the 26s Rom ? Because that fixes it.
chetermaat said:
Mine worked perfectly untill I flashed let max 2 day after arrival. It has something to do with the bootloader. Because I got the 26s version bootloader in it and now it works while using pure nexus droid
Click to expand...
Click to collapse
You mean those never flash any firmware, never have their fingerprint dead?
So if I am still stock, I should not flash anything to preserve fingerprint functionally?
kkcheong said:
You mean those never flash any firmware, never have their fingerprint dead?
So if I am still stock, I should not flash anything to preserve fingerprint functionally?
Click to expand...
Click to collapse
Yes. Or flash the 26s version. It's official dev for our max 2. After flashing the 26s you may root. Install TRWP 3.0.2.0 not higher. And when you installed TRWP you may flash pure nexus on your le max 2. The fact losing fp functionality must have something to do with bootloader and or combined with TRWP.
chetermaat said:
Yes. Or flash the 26s version. It's official dev for our max 2. After flashing the 26s you may root. Install TRWP 3.0.2.0 not higher. And when you installed TRWP you may flash pure nexus on your le max 2. The fact losing fp functionality must have something to do with bootloader and or combined with TRWP.
Click to expand...
Click to collapse
Not true at all first you can flash anything and FP still work. Before I bough X820 and come back home, after 2 hours FP stop working while on stock rom that came with the phone. So I returned it the next day and get the Le Pro 3 in stead. It's hardware fault.
Why dont just update the modem for 23s chiinese version, wipe cache, dalvik, data (not internal storage) and system then flash a new rom and test if the FP back to work? its a simple test way.
On mine i have it for 3 months now, on first day i have updated the modem for 23s version, and the FP never stops working.
i bought mine from china , I got the same issue after 2 weeks , it happened as a result of using the FP while charging , I took it to the service center and there where many people with the same issue with FP and the same reason as I had , they had to replace the sensor with a new one.
they told it might be because of the heating effect of charging with a static overload on the sensor .
try cleaning with isopropanol or throw away
Gesendet von meinem LEX820 mit Tapatalk
Moon75 said:
Not true at all first you can flash anything and FP still work. Before I bough X820 and come back home, after 2 hours FP stop working while on stock rom that came with the phone. So I returned it the next day and get the Le Pro 3 in stead. It's hardware fault.
Click to expand...
Click to collapse
Like I said. If you first flash the 26S version FP wil work
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Reflash TRWP 3.0.2.0
Reflash your taste of Droid
Reroot with superuser via TRWP
You should still have FP.
Most important is the 26S version at first
chetermaat said:
Like I said. If you first flash the 26S version FP wil work
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Reflash TRWP 3.0.2.0
Reflash your taste of Droid
Reroot with superuser via TRWP
You should still have FP.
Most important is the 26S version at first
Click to expand...
Click to collapse
You mean like now if I flash any 26S stock rom it might be fix?
Is there a guide for what you mentioned here? thanks
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
chetermaat said:
Like I said. If you first flash the 26S version FP wil work
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Reflash TRWP 3.0.2.0
Reflash your taste of Droid
Reroot with superuser via TRWP
You should still have FP.
Most important is the 26S version at first
Click to expand...
Click to collapse
Can you point me to the 26s firmware file you used for this?
Or the thread where you found it?
Looks like I'm blind
Moon75 said:
You mean like now if I flash any 26S stock rom it might be fix?
Is there a guide for what you mentioned here? thanks
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Click to expand...
Click to collapse
JamBax said:
Can you point me to the 26s firmware file you used for this?
Or the thread where you found it?
Looks like I'm blind
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BxPg20xeuX4JekZEcjNKWEpCcEk/view
chetermaat said:
https://drive.google.com/file/d/0BxPg20xeuX4JekZEcjNKWEpCcEk/view
Click to expand...
Click to collapse
I asked beacuse it did not work with aurel's version, so I wanted to make sure I use the right version.
Another question, is anything known about differnt versions of the fingerprint sensors, different manufacturer?
Is it the same fingerprint as in other devices X52x or X62x??
Is there a way to read out if the system recognizes FP sensor?
How long should it take to calibrate FP? It is written 2-3 minutes, but when the sensor is dead, it only takes about 20 seconds??
I did this and after months of trying to get my finger print reader to work trying all the "fixes" people have posted, and finally mine works again. I am and was using the RR Rom 7/13/17 & Open Gapps, I didn't follow your step exactly but my finger print reader works perfectly and quickly now.
What I did:
Flashed Modem 26s : https://yadi.sk/d/woKdrlRrv8yhr/Китай (modem_cn_26s_v00033.zip)
Flashed TWRP 3.0.2-1 : https://dl.twrp.me/x2/twrp-3.0.2-0-x2.img.html
( Fastboot flash recovery TWRP-3.0.2-x2.img )
Flashed RR 7/13/17 over my current flash no wipe (besides dalvik/cahce)
waited for it to boot, went into settings and boom it worked first try no issues... FINALLY A WORKING FP Sensor again, Thanks I owe you one. The flashing order seems to be critical as i have done similar to this with no success....
kintera said:
I did this and after months of trying to get my finger print reader to work trying all the "fixes" people have posted, and finally mine works again. I am using the RR Rom 7/13/17 & Open Gapps, I didn't follow your step exactly but my finger print reader works perfectly and quickly now.
What I did:
Flashed Modem 26s
Flashed TWRP 3.0.2-1 : https://dl.twrp.me/x2/twrp-3.0.2-0-x2.img.html
( Fastboot flash recovery TWRP-3.0.2-x2.img )
Flashed RR 7/13/17 over my current flash no wipe (besides dalvik/cahce)
waited for it to boot, went into settigns and boom it worked first try no issues... FINALLY A WORKING FP Sensor again, Thanks I owe you one. The flashing order seems to be critical as i have done similar to this with no success....
Click to expand...
Click to collapse
Which ROM were you using before flashing 26s modem?
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?
I don't know about mac, but imei is ok
When I try to enable wifi (or bluetooth), it says 'Turning on...' underneath the icon but the process never succeeds.
Note:
-Under About > Status I see no MAC address for Wifi or Bluetooth.
-Phone is not rooted.
-Bootloader is unlocked.
-No custom recovery.
-Airplane mode is off.
-I am able to access the internet when I put in my SIM card and use my cellular data.
-EDIT: Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
-EDIT: I keep my SIM out of this phone (it's in my fully working phone). Can insert if need be.
My attempts to solve this issue (none have worked):
-I updated to OxygenOS 11.
-I booted into recovery and wiped everything, including cache. I also did a System Reset.
-I went to Settings > System > Reset Wifi, mobile and Bluetooth. I also did Erase all data (factory reset) in the same place.
Is there anything else left to try? Is there a way to flash the modem image maybe, I remember having to do that with my Nexus 4 many years ago.
Thanks!
A factory reset never finds the root cause. A virus or an old load are the only reasons to use it otherwise find the root cause. Usually a bad setting. If it's software caused the solution is right in front of you.
Network reset, worth a shot.
Clear system cache, can't hurt.
Clear data in sim card tool kit apk.
Both are probably redundant since you already did a hard reset, but try anyway.
Otherwise...
Bad sim card (try reseating it or replace otherwise) , corrupted firmware, or defective hardware.
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
dladz said:
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
Click to expand...
Click to collapse
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
bassamanator said:
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
Click to expand...
Click to collapse
Ah yea that's not good. 2025 AFAIK is global mainly sold in the US.
The MSM tool is in discussion I believe and it's a tool you use to restore your phone using EDL mode, to get to EDL.
Power off your phone.
Connect it to your computer (if it turns on again turn it back off)
Then open up the MSM tool and press and hold volume up and down
Your computer will recognise the the device and at this point you should start the process as it will try again to reboot shortly after without any input from you.
This is the thread you need.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Bare in mind this will relock your bootloader but it's easy to get that back unlocked.
Any questions regarding the tool just ask in the thread.
(you shouldn't need to providing you download the right one)
Download the latest firmware within the tool. If you get stuck don't just guess, ask someone.
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
bassamanator said:
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
Click to expand...
Click to collapse
But now you have bt?
blackhawk said:
But now you have bt?
Click to expand...
Click to collapse
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
bassamanator said:
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
Click to expand...
Click to collapse
How/when did it start? Anything happen to the phone?
bassamanator said:
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
Click to expand...
Click to collapse
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
blackhawk said:
How/when did it start? Anything happen to the phone?
Click to expand...
Click to collapse
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
bassamanator said:
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
Click to expand...
Click to collapse
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
dladz said:
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
EDIT: the phone has 2 IMEI numbers.
bassamanator said:
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
Click to expand...
Click to collapse
I've already posted in the MSM thread for you.
What about your fingerprint? Is that still working?
dladz said:
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
Click to expand...
Click to collapse
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
bassamanator said:
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
Click to expand...
Click to collapse
Yea for me it does, it shows there's a correlation between the persist problem and the EFS problem and a direct connection to your IMEI or Mac address issue.
With this in mind I would recommend the persist.img fix thread..
Getting that working may be key to solving the Mac / IMEI problem.
At this point nothing is going to hurt.
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
dladz said:
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
Click to expand...
Click to collapse
I was about to say, I want to try something along the lines of
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Click to expand...
Click to collapse
or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
bassamanator said:
I was about to say, I want to try something along the lines of or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
Click to expand...
Click to collapse
Ok don't do the EFS fix you do not have an EFS back up.
Give this a shot
go to data/misc/wifi (required root)
-backup file wpa_supplicant.conf in this folder which contains usename and password wifi
- delete all file in this folder
- turn on wifi ( if you careful, you can reboot )
- now you can connect to wifi
- recovery file wpa_supplicant.conf
This isn't my writing. The English is a little broken but you get the point
Hi all,
I had a lot of issues after I had my screen replaced, the fingerprint sensor will not work after that. I reset everything with msmdownloadtool, and because it still does not work, I need a persist partition from someone, so I can fix my sensors and afterwards I will delete the file.
So I would like to please ask someone to perform the following adb actions and share the persist partitions image file with me.
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit
I will be extremely thankful. And so will my wife for who I am repairing the phone after she dropped it...
Post 153 has a persist.img shared in this group. Although from all I have read the persist.img should be your own.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
FreshlyBaked 420 said:
Post 153 has a persist.img shared in this group. Although from all I have read the persist.img should be your own.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Click to expand...
Click to collapse
Hey FB, yeah, you might be right about how it needs to be my own. I have my own backuped, but because of this nasty error I'm just gonna try it out and see what works. Thank you so much for finding this for me. I really hope it helps.
voidzero said:
Hey FB, yeah, you might be right about how it needs to be my own. I have my own backuped, but because of this nasty error I'm just gonna try it out and see what works. Thank you so much for finding this for me. I really hope it helps.
Click to expand...
Click to collapse
No worries, good luck. There's a couple guide the the 8P guide section you should read though.
FreshlyBaked 420 said:
No worries, good luck. There's a couple guide the the 8P guide section you should read though.
Click to expand...
Click to collapse
I've been searching, and scrolling and looking... I'm struggling with this one now:
How to Fix Loss Of Fingerprint Sensor Issue on any OnePlus Device
In this comprehensive tutorial, we will show you detailed steps to fix the loss of fingerprint sensor issue on any OnePlus device.
www.droidwin.com
And right now I got my fingerprint sensor to work right after a failed calibration. But reboot once and the fp sensor no longer works again, hardware failure... purportedly.
I had issues with mine, tried multiple ways to get it back. Never did have any success, so I tried contacting OP for repair. All they tried was the MSM tool with a remote session. I ended up returning it under warranty.
Did OnePlus replace the screen or did you? Or was it third party replaced? If it was OP I'd contact them.
FreshlyBaked 420 said:
I had issues with mine, tried multiple ways to get it back. Never did have any success, so I tried contacting OP for repair. All they tried was the MSM tool with a remote session. I ended up returning it under warranty.
Did OnePlus replace the screen or did you? Or was it third party replaced? If it was OP I'd contact them.
Click to expand...
Click to collapse
It was a local repair shop. I might try to return it under warranty anyway and see what they'll say. Unbelievable how obtuse this stuff is.
I have a oneplus 8 pro, and experimenting with it I messed up the fingerprint, I had already made the copy of persist and then now trying other solutions the camera also stopped working and I can't flash my persist.img to see if it's solved, I get it the error message remote critical partition, I already tried to do the fastboot flashing unlock_critical but it keeps giving me the same error, if I try unlock_critical again I get the message device already unlocked, sorry for my bad English
idk if there are better ways but i would use msm tool and start over
xtcislove said:
idk if there are better ways but i would use msm tool and start over
Click to expand...
Click to collapse
I already did it many times but that doesn't affect persist that's why I need to flash...
ddav_23 said:
I already did it many times but that doesn't affect persist that's why I need to flash...
Click to expand...
Click to collapse
I would use MSM tool, unlock bootloader and then follow this thread for example.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
xtcislove said:
I would use MSM tool, unlock bootloader and then follow this thread for example.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Click to expand...
Click to collapse
I just had that problem after trying that guide... what happens is that people lost the fingerprint because yes, I instead decalibrated it by manipulating the engineer mode... And I didn't save a copy of my persist before... So I can't follow the tutorial anymore to fix my reader... I seem to be misunderstanding... I just need someone to help me To be able to flash my persist, I need to be able to do "unlock_critical" and not tell me giving an error in fastboot when trying...I don't need any msm or anything like that... Thanks my friends
Or in the same way to be able to fix the camera error that does not open and remains on a black screen... The flashlight gives the camera in use error and cannot be used either..
As far as i know some people got it fixed with relocking the bootloader and starting over.
fastboot flashing unlock_critical should work and what i found if it not works people used MSM tool to start over.
Thats why i suggested this.
I suggest you already tried to use MSM tool?
What are the steps you already tried so far if not?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
xtcislove said:
As far as i know some people got it fixed with relocking the bootloader and starting over.
fastboot flashing unlock_critical should work and what i found if it not works people used MSM tool to start over.
Thats why i suggested this.
I suggest you already tried to use MSM tool?
What are the steps you already tried so far if not?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
As I already mentioned, sorry if my English is not well understood... I have already opened and closed the bootloader about 10 times... I have also used MSM several times... the version with Android 10 I don't remember the exact number But it's the same as mentioned in the thread to recover the fingerprint... My only hope is to be able to achieve "fasboot flash persist..."
I already saw that I must do "fastboot flashing unlock_critical" but even after it continues to appear that critical partitions cannot be flashed