Related
Hi All,
Im having an issue with a fingerprint enrolment issue. The sensor does not load. I have tried the MSMtool but its still the same. On the MSM thread it says I may need a Persist partion?
I have the EU model.
It would be a life saver if you could upload it!
Thanks
Here you find some FASTBOOT images probably you will find what you need
https://sourceforge.net/projects/fastbootroms/files/OnePlus 8 Pro/
Thanks i will have a look
Just checked, persist isn't in the rom. Still require a backup if anyone's got a rooted EU model
For anyone with a rooted eu model. You can use this app to backup the persist partition
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en
Still looking for this if anyone can help with a rooted EU model. Seen another couple of members with the issue so might be worth while to keep this hosted for people anyway.
Hi,
I face the same issue with the Fingerprint sensor not working (can't even register).
Can you please give me a hint where to find more info on what you are trying to achieve by getting the persist image?
Right now I have two concerns :
- does sharing an image from a device having the error make sense at all?
- from my (very limited!) understanding the persist image contains also things like WiFi MAC and other maybe device dependent information - if you flash the partition with someone's else's doesn't this basically overwrite critical information of your own device?
Thanks,
Axel
From my research it's the persist partion that makes the sensor work. It usually gets corrupted it you flash the wrong version of software.
Im not sure on the fine details but it apparently works. It's listed on the MSMdownload thread as a fix as well
https://forum.xda-developers.com/7t-pro/help/request-persist-partition-t4060997
https://forum.xda-developers.com/oneplus-6t/help/persist-img-partition-6t-sensor-broken-t3907577
https://forum.xda-developers.com/oneplus-7-pro/help/request-persist-img-t3935511/amp/
Guitarfreak26 said:
https://forum.xda-developers.com/7t-pro/help/request-persist-partition-t4060997
https://forum.xda-developers.com/oneplus-6t/help/persist-img-partition-6t-sensor-broken-t3907577
https://forum.xda-developers.com/oneplus-7-pro/help/request-persist-img-t3935511/amp/
Click to expand...
Click to collapse
I have the same issue , i hope that it will be fixed
How did you guys get the issue ? This seems pretty widespread.
I hadn't crossflashed anything prior to this happening. Just flashed Europe stock boot and then factory reset
I just used the MSM tool , i flashed the BA version , because my op8p is eu model , and since then it does not work
Verstuurd vanaf mijn IN2023 met Tapatalk
Really strange. I haven't seen this issue on previous models. Maybe OnePlus actually shipped international models to us and we've used EU software? I really don't know
I feel so stupid for not backing up the Persist partition ??
Here you go;
Persist partition from EU phone...
I'm on 10.5.5.
Thank you now need to work out how to flash with dd lol
Guitarfreak26 said:
Thank you now need to work out how to flash with dd lol
Click to expand...
Click to collapse
You can restore with the same app.
Don't think the App works for restores. It needs a DD command I just need to figure out what they are lol
Guitarfreak26 said:
Don't think the App works for restores. It needs a DD command I just need to figure out what they are lol
Click to expand...
Click to collapse
Well, the app gives the option for restoring partitions, I'm just not brave enough at the moment to do it on the spot
I did haha but it says not a recognised image. Need to do it via dd. As soon as I work out the command I'll try it
If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.
We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.
t-mizzle said:
We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.
Click to expand...
Click to collapse
ive done used MSM Brick Fix along with just about every other stock. Nothing has worked only reason i am so panicky over it is being used for a project that im working on and really need all features to work
Is this for Global or EU? Have a look in my thread if you need an EU persist. I ended up bricking mine trying to fix it.
This seems quite a wide spread issue, MSM doesn’t fix it either
If no one can provide you with a fix, I would use adb to flash the stock boot image. If you are wiped and fully stock again, did you go through the setup again, if so, did the enrollment fail there or did it fail when you manually went there? I just don't see why it would fail when the phone is in the stock "first bootup" mode.
It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.
Interesting. Did you at any point have a working fingerprint scanner? I did, until I rooted.
Guitarfreak26 said:
It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.
Click to expand...
Click to collapse
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Dewaynelives said:
If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.
Click to expand...
Click to collapse
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool
Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?
Guitarfreak26 said:
Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?
Click to expand...
Click to collapse
Ot..Oneplus Finland sound funny..Cause its a Chinese company and i am Finnish myself
Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
Click to expand...
Click to collapse
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool
Nekromantik said:
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool
Click to expand...
Click to collapse
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking
dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
pyry666 said:
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking
Click to expand...
Click to collapse
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.
Guitarfreak26 said:
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.
Click to expand...
Click to collapse
I know that. I am interested is it msmtool failure or something in os
From my understanding from looking across the forums the persist partion hasn’t been touched by MSM for a while. Which would mean it’s an OS fault.
Does the boot img even touch the persist partion as that’s the only thing that had been touched prior to the fault? I don’t have enough understanding on persist as I’d never seen the issue before lol
pyry666 said:
I know that. I am interested is it msmtool failure or something in os
Click to expand...
Click to collapse
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw
Nekromantik said:
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw
Click to expand...
Click to collapse
Im on Int version is there any way for me to fix it? i dont know anyone with the device myself so i have no way to get the file
Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool
Click to expand...
Click to collapse
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?
Dewaynelives said:
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?
Click to expand...
Click to collapse
Well, in my case it has been caused by a factory reset. Yes, I was rooted before that, but everything worked fine - so maybe rooting was the cause and it became evident after the reset.
Oh, and I was only on EU ROM - so no cross-country flashing.
I'll wait for Oneplus fixing this, for me there is too little understanding what happens when flashing persist from a different phone.
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
I havent seen anyone post a thread for this issue yet, so I will, since I've already seen that I'm not the only one.
I got forced to update to OOS11 after deferring the update for as long as I could. And it's soft bricked my phone. I can boot the stock boot image, but not any images magisk patched by either me or others, flashed or through fastboot boot. After around 5 minutes running the stock boot image it crashes to qualcomm crashdump mode unless i immediately put it into airplane mode to shut off the modem.
This is the dump it gives me:
Code:
ssr:return:MPSS:qmi_oem_svc.c:1310:oem:go_to_error_fata
SDX5x esoc0
modem crash
mdm_get_restart_reason
I can boot into TWRP at least via fastboot boot, so there's that.
All I can think of at this point is to use the msm tool to unfuck my device. But my understanding is that will wipe my phone, and I'm trying to exhaust all other options before turning to that as I really, really, don't want to have to spend four hours setting my phone back up and moving my data back onto it.
Is there any way that I could make the backup and restore process quicker without twrp being able to decrypt anything? Being able to boot a rooted image would at least be a start to that, so I could use titanium backup, but I cant boot a patched image, so I cant make a backup. I was actually going to make one this week before this happened, I'd just been procrastinating.
Stop asking identical questions in multiple places! I already answered you
starcms said:
Stop asking identical questions in multiple places! I already answered you
Click to expand...
Click to collapse
You're talking about someone else, you've never replied to me before. The only other posts I've made on the issue have been agreeing with other people who have also had the same issue. And if thats a problem, well frankly I don't care.
Jvk1166z said:
You're talking about someone else, you've never replied to me before. The only other posts I've made on the issue have been agreeing with other people who have also had the same issue. And if thats a problem, well frankly I don't care.
Click to expand...
Click to collapse
No, it was definitely you because I remember answering that exact question, word for word. I'm not sure if it was a duplicate thread that has now since been deleted by admins or a post in someone else's thread, but I most certainly read it and answered it.
Anyway, in case it was deleted or you missed it, it sounds like your radio's baseband (firmware) got corrupted.
You can try going into bootloader and doing
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
and see if that helps. If not, you are going to need to run the MSM tool to fix it.
Also, TWRP backups don't properly restore on our device, so no real point in making any. I think it will backup and restore boot property, but that's about it. Definitely not system nor data. Will never boot if you try restoring either. If you want to make backups, use the MSM tool.
Swift Backup is also much more reliable for making app data backups than TiBu in Android 10+ (although I still keep TiBu installed and still use it for other things just because I've been using it for 10+ years). Combine with OnePlus's backup and restore app, and it's a very quick, reliable restore of app and system settings amongst everything else.
Edit: And the reason it won't boot at all with the Magisk injected boot image is most likely that you have some Magisk module enabled which isn't compatible with OOS11. You should always disable all modules b4 any updates; good chance that possibly caused your issue in first place.
starcms said:
No, it was definitely you because I remember answering that exact question, word for word. I'm not sure if it was a duplicate thread that has now since been deleted by admins or a post in someone else's thread, but I most certainly read it and answered it.
Anyway, in case it was deleted or you missed it, it sounds like your radio's baseband (firmware) got corrupted.
You can try going into bootloader and doing
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
and see if that helps. If not, you are going to need to run the MSM tool to fix it.
Also, TWRP backups don't properly restore on our device, so no real point in making any. I think it will backup and restore boot property, but that's about it. Definitely not system nor data. Will never boot if you try restoring either. If you want to make backups, use the MSM tool.
Click to expand...
Click to collapse
I have no idea then, because I've only posted this exact post once, maybe it double posted or something.
Either way, I wish I saw your reply earlier, I already resorted to the msm tool and wiped my phone a few minutes ago. But I'll try this if it breaks again for sure. Since I was able to get it to run with airplane mode, I didn't lose any data at least, just lots and lots of configuring to do.
Thanks for the help though.
Jvk1166z said:
I have no idea then, because I've only posted this exact post once, maybe it double posted or something.
Either way, I wish I saw your reply earlier, I already resorted to the msm tool and wiped my phone a few minutes ago. But I'll try this if it breaks again for sure. Since I was able to get it to run with airplane mode, I didn't lose any data at least, just lots and lots of configuring to do. Thanks for the help though.
Click to expand...
Click to collapse
99% chance you would have had to run the MSM tool anyway to fix it, so don't feel bad. Glad it got u back up and running and didn't have deeper corruption in persist or param partitions which MSM tool restore can't help you with. Hopefully you've already backed those up and have them stored safely in at least 2 different places.
starcms said:
99% chance you would have had to run the MSM tool anyway to fix it, so don't feel bad. Glad it got u back up and running and didn't have deeper corruption in persist or param partitions which MSM tool restore can't help you with. Hopefully you've already backed those up and have them stored safely in at least 2 different places.
Click to expand...
Click to collapse
I actually did backup everything in the F8 menu of the MSM tool right before doing the restore, and my fingerprint sensor was working in airplane mode so I'm assuming my persist partition was fine.
I'll remember to disable my modules next time. Never had them break like this before so I never thought to disable them.
Jvk1166z said:
I actually did backup everything in the F8 menu of the MSM tool right before doing the restore, and my fingerprint sensor was working in airplane mode so I'm assuming my persist partition was fine.
Click to expand...
Click to collapse
Yes, if FP sensor is working, your persist is fine, but you should still definitely have a backup because just random things can cause it to become corrupted pretty much any time. A bad canary version of Magisk corrupted mine. It's just dumb luck if yours hasn't become corrupted yet.
Also, running the NSG app can cause your param partition to become corrupt and lose the ability to connect to SA 5G amongst other things (such as making HD+ calls).
However, unlike persist which never ever is supposed to be changed, param is occasionally updated by OTA updates. It was updated by the OTA to OOS11. So while you only need to make one backup of persist, you should regularly backup param after each update to be completely safe. Because the MSM tool restore won't help you if param is corrupt.
Long story short, I bricked my device very hard, very many times while trying out different ROMS and getting accustomed to handling fastboot and adb. At some point along the journey I must've broken something to do with the fingerprint sensor (or the security authentication method)? The sensor doesn't pick up anything when I have my finger on it, as if I had replaced the screen or something. This happens with all ROMS, including after doing a full reset to factory images and running Nothing OS. Maybe a driver or something?
I was using NOS 1.1.6 and and reset to the image that I found on https://reindex-ot.github.io/
There is now also a 1.1.7 ROM but I haven't tried updating to it yet, though I will at some point.
I have no idea how this actually works so any help would be appreciated. If there is a fingerprint calibration method, a piece of software to help or a certain stock img file that is needed then please leave a reply!
For now I have been using Face Unlock as a drop in replacement, although the algorithm and sensors don't provide for as quick and reliable authentication as the fingerprint sensor, so I would really like to get this fixed.
It also kinda forces me into using Paranoid Android right now as it has best Face Unlock that I've come across so far, and being able to authenticate quickly is worth most of the downsides that come with using it at this stage of development.
Calibrating the fingerprint sensor may improve the situation. The site introduced here is in Japanese.
Relife RL-071Bで光学式画面内指紋認証センサーの動作を修正する方法 - AndroPlus
画面内指紋認証センサーを搭載したAndroidスマホで指紋を登録できなくなったときの対処法を紹介します。 キャリブレーションし直しで解決できる場合あり 画面内指紋認証センサーを搭載したAndroidスマートフォンでは、特にBootloader
androplus.org
ot_inc said:
Calibrating the fingerprint sensor may improve the situation. The site introduced here is in Japanese.
Relife RL-071Bで光学式画面内指紋認証センサーの動作を修正する方法 - AndroPlus
画面内指紋認証センサーを搭載したAndroidスマホで指紋を登録できなくなったときの対処法を紹介します。 キャリブレーションし直しで解決できる場合あり 画面内指紋認証センサーを搭載したAndroidスマートフォンでは、特にBootloader
androplus.org
Click to expand...
Click to collapse
I read through the article and tried all the methods but I couldn't get anything to happen when I dialled. Thanks so much for the help though!
I think the reason my sensor is not working is because I flashed a persist partition when I was unbricking my phone, maybe if i flash a recent persist partition it will fix the fingerprint issue? Maybe it wont, not sure if something like that needs to be calibrated at the factory?
Either way, I am willing to try...
If anyone has a factory persist.img for Phone 1 that might help?
Ideally Nothing OS 1.1.6 full factory setup, but 1.1.7 will also help a lot as I can update.
Any post is appreciated!
I will put out a persist.img. I hope this fixes it.
NothingPhone(1)_Persist.zip
Nothing Phone(1) persist
drive.google.com
ot_inc said:
I will put out a persist.img. I hope this fixes it.
NothingPhone(1)_Persist.zip
Nothing Phone(1) persist
drive.google.com
Click to expand...
Click to collapse
Can I ask what version this is from?
jhonnytable said:
Can I ask what version this is from?
Click to expand...
Click to collapse
v1.1.7