Database Users

Can anyone share a dump folder of .ops file? (python)

*EDIT 05-24
I had a problem where I would get stuck even after using MSMDOWNLOADTOOL completely. With the help of great minds,
#fullofhell #Dark Nightmare #Scott and frankly a god #Eliminater74 I could fix the phone completely. I am heading for modem work, which put me into this situation.
As of this point, I cannot find any misbehavior but I am quite new to this, so I can be deadly wrong. (Well but then, sensors are fine, calls , texts, data, wifi is working just fine. I don't know what else to check!)
I know as a fact that what happened to me is not really that rare (although it is quite rare, it happened before as well.)
So I was about to share how I fixed it but decided not because what I did was so out of experimental and I frankly have no idea if the same would work for others.
Tbh, if you are in the same position as I am, go ahead and contact the Oneplus service team. I did what I did only because I had to, I am Korean, and couldn't get it fixed.
If anyone, comes to this point and has absolutely no way to get it fixed, I will be glad to help,
(only if that person agrees that there is more chance to totally destroy it then fixing it XD.)
Again, Thank you so much Scott, dark nightmare. What you guys shared with me saved a bunch of time and you guys are what the forum truely needs!
P.S, Still couldn't find the moded MSMdownload tool. What can you recall what functions it had? Maybe enabled engineer mode?

I can't assist with your dump file, I'm just curious though how exactly did you brick your device?

Pain-N-Panic said:
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Click to expand...
Click to collapse
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!

Somehowko said:
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Click to expand...
Click to collapse
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?

Pain-N-Panic said:
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Click to expand...
Click to collapse
As the bootloader is locked and I cannot boot, I am can't put enable oem-unlock on the data. Which means, yes I cannot unlock the bootloader as long as oneplus 6t doesn't have a loophole like oneplus 3T. I am pretty sure that was fixed though.
Well, I don't know if it's msm tool really. If I just started with that I would have been fine (at least I believe so). Yes I didn't wanted to lock the boot loader, which is why I used fastboot flash tool. But then, that's why I ended up here. So, if you end up in a situation where you might, might need msm tool or flash tool, always go with the msm tool !
For msm, I am quite certain it doesn't flash all partitions. I think there is some partition checkup somewhere. Here is why I think so
1) Completely formatted OS cannot be on a boot loop unless it's caused by hardware issue.
2) All partitions except vendor, system goes way too fast. It ends within 200 seconds for me. I would assume that kinda makes sense as it really is the problem of usb-pc hardware power but installing the image should take longer I think (but then I truly have no idea)
My conclusion is that the tool checks partition size before flashing, and does not touch / replace every file. I am probably wrong since it is
EDI tool after all, but I simply cannot believe msm tool cannot fix something that has nothing to do with the hardware.
I mean, imagine we can brake our newly formatted PC OS without any single components corrupted! (Is it even possible?)

I don't know man....with the bootloader locked you're not able to fastboot flash ANYTHING?

Somehowko said:
For msm, I am quite certain it doesn't flash all partitions.
Click to expand...
Click to collapse
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145

Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Well, tbh, we know as a matter of fact it is not a complete flashing. I mean it clearly says flashing to partition _a only unlike previous versions of msm tools (ah, good days.) What I am curious of is if there is anything we can do about skipping partitions. I am suspecting using qfil would, through unpacking ops files. Although it seems like a long shot.
Btw, thank you for your interest!

Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Siren siren... Watch out the xda police gunna blow down and remove my comment.. oh nooooo aghastt....
Btw u cannot use berklers script without an AES recovery key. There aren't any around as far as I know for fajita.
Easiest thing is if OnePlus bought device, get an exchange.. play dumb.. oops I dunno, your Android Q crap broke it..
Or if tmo bought, add insurance if u don't have it, play dumb. Get a new one. I did for a scratched screen..but made it about the modem not working, bc I erased it...
These corporations owe us nothing.
Get a new phone man

fullofhell said:
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Get a new phone man
Click to expand...
Click to collapse
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!

Somehowko said:
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Click to expand...
Click to collapse
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I believe, just look for the modded tool that skips the model check, did you do a full system backup before tinkering? If so you can dd files back into place if msm doesn't overwrite them the way its supposed to, I've done some crazy things to the 6t, a bit surprised recovery didn't fix it for you...
And yeah FoH already pointed out that decrypt tool is useless to us.

Dark Nightmare said:
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I .
Click to expand...
Click to collapse
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?

Somehowko said:
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Click to expand...
Click to collapse
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.

Dark Nightmare said:
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Click to expand...
Click to collapse
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!

Somehowko said:
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Click to expand...
Click to collapse
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?

Dark Nightmare said:
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Click to expand...
Click to collapse
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!

Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
That's correct and if you're on windows 10 it may be a system update messing with the drivers, its dumb, but it actually affects the simplest of things.

Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
As crazy as it sounds three reboots and four different ports did the trcik!
And sincerely thank you! Although I couldn't find the modded msmtool you told me I was able to boot into the os finally.

Mobvoi TicWatch S2 / E2 Rom needed.

Hey folks..
Due to bad luck my TicWatch S2 died during a firmware update process. (I was not flashing...the system was)
It seems that the boot.img got corrupted and now it will not boot at all.
Fastboot is still working so i thought i might be able to just flash the original stock firmware.
Which is exactly what brought me here.... I can not find it anywhere on the web.
I have emailed MobVoi but of course there was no response.
They suggested to send it in but this is just no feasible since the watch will be gone for at least 3 months...costs involved etc etc.
Makes no sense to send anything back to china these days.
My current rom is/was : PWDR.190618.001.A1
It would be great if someone could help me out here.
Or even a way to root it since a friend of mine has the same watch but we do not have the means to extract the ROM without root.
Nicolas

Does anyone know how to Extract img files from a backup via fastboot? Apperantly, the Ticwatch E/S2 can easily be unlocked. Should I know how to get the files, I'd gladly share them for recovery and development purposes.

lordsolrac2 said:
Does anyone know how to Extract img files from a backup via fastboot? Apperantly, the Ticwatch E/S2 can easily be unlocked. Should I know how to get the files, I'd gladly share them for recovery and development purposes.
Click to expand...
Click to collapse
fastboot oem unlock is all that is needed to unlock them.
As far as I know there is no way to grab the recovery or boot image through fastboot tho.
While in recovery the abd is disabled so that is a no go too.
If you know of a way to create a 'fastboot' backup ..please let me know.
Nicolas

Good News! I've digged a bit and got to make a backup! You do however, need to use TWRP, that means unlocking the bootloader if you are able.
The Ticwatch E/S2 doesn't have an officially supported TWRP image, however, I used the Ticwatch C2 because it's the same CPU. You could try to use another ticwatch's image, though. For the C2, however, there was an offset on for the buttons. I'll be uploading my backup as soon as I can

lordsolrac2 said:
Good News! I've digged a bit and got to make a backup! You do however, need to use TWRP, that means unlocking the bootloader if you are able.
The Ticwatch E/S2 doesn't have an officially supported TWRP image, however, I used the Ticwatch C2 because it's the same CPU. You could try to use another ticwatch's image, though. For the C2, however, there was an offset on for the buttons. I'll be uploading my backup as soon as I can
Click to expand...
Click to collapse
Thats really great news :good:
I have tried to use the Pro and C2 twrp. But it simply would not boot into it.
fastboot boot TWRP-C2.img kind of thing

Finally got home to see it finished!
Backup : https://mega.nz/#!GUMXQSRb!LD2SioJC_A7kOCTyKHfSRAmDkG67aDprf8UYUYHYZFM
Mobvoi TWRP : https://twrp.me/Devices/Mobvoi/ - Personally I used the C2, but I noticed Pro (catfish) is also a Snapdragon 2100
Lemme know how it goes for you. I might make a post so any interested devs get into it.
Also it's WearOS update H

lordsolrac2 said:
Finally got home to see it finished!
Backup : https://mega.nz/#!GUMXQSRb!LD2SioJC_A7kOCTyKHfSRAmDkG67aDprf8UYUYHYZFM
Mobvoi TWRP : https://twrp.me/Devices/Mobvoi/ - Personally I used the C2, but I noticed Pro (catfish) is also a Snapdragon 2100
Lemme know how it goes for you. I might make a post so any interested devs get into it.
Also it's WearOS update H
Click to expand...
Click to collapse
Awesome :good:
Going to try it ASAP.
Personally, I could not get any of the twrps to boot at all...and I do not want to permanently flash it since i do not have the original.
Skipjack seems to be the best bet but looking at the git repo i do not see why it will not boot.
Weird...will keep at it tho.
Nicolas
Edit...i guess that bricked it.
I am just getting a black screen with
Device software can't be checked for corruption.
To pause boot press side button.
I can not even get back into fastboot mode. Ah crap.
If i could only find the test points for the bootloader

wish there is a way that I can switch my S2 to international ROM....

Nicolas72 said:
Awesome :good:
Going to try it ASAP.
Personally, I could not get any of the twrps to boot at all...and I do not want to permanently flash it since i do not have the original.
Skipjack seems to be the best bet but looking at the git repo i do not see why it will not boot.
Weird...will keep at it tho.
Nicolas
Edit...i guess that bricked it.
I am just getting a black screen with
Device software can't be checked for corruption.
To pause boot press side button.
I can not even get back into fastboot mode. Ah crap.
If i could only find the test points for the bootloader
Click to expand...
Click to collapse
Holy hell.... could you send it for repair? O_O Seems to me the boot partiton was in fact damaged. As for the test point I do not know. :c

lordsolrac2 said:
Holy hell.... could you send it for repair? O_O Seems to me the boot partiton was in fact damaged. As for the test point I do not know. :c
Click to expand...
Click to collapse
Sending it back is really not an option. Mobvoi is notorious for taking forever to even process your request.
Plus..sending it back and forth...with an unlocked bootloader etc etc...they will just say it was my own damn fault.
Which in a way it was. Should have sent it back when it first happened if anything.
I managed to get the watch into QDL mode tho. Not that his helps me much since i do not have the firmware binaries needed for that mode.
Can you put your S2/E2 into fastboot without using adb commands ? Like with the old E it was keeping the button pressed..waiting for vibration then press again a few times.
With the S2/E2 this does not work any more.
It can only be the boot that is damaged..nothing else. So the watch itself is pretty much still functional.
In case i figure it out i will post the details here.
Nicolas

Did anyone ever come up with a working twrp file for the TicWatch E2 or verify that the C2 TWRP one works?

Anyone get this to work with the TicWatch E2? Can the E2 be flashed with TWRP image from either TicWatch C2 or Pro image?

lordsolrac2 said:
Finally got home to see it finished!
Backup : https://mega.nz/#!GUMXQSRb!LD2SioJC_A7kOCTyKHfSRAmDkG67aDprf8UYUYHYZFM
Mobvoi TWRP : https://twrp.me/Devices/Mobvoi/ - Personally I used the C2, but I noticed Pro (catfish) is also a Snapdragon 2100
Lemme know how it goes for you. I might make a post so any interested devs get into it.
Also it's WearOS update H
Click to expand...
Click to collapse
Is this twrp backup you uploaded from an S2 or E2 or should it work for both models? Thank you

TechJourney12 said:
Is this twrp backup you uploaded from an S2 or E2 or should it work for both models? Thank you
Click to expand...
Click to collapse
It's from an E2

lordsolrac2 said:
Finally got home to see it finished!
Backup : https://mega.nz/#!GUMXQSRb!LD2SioJC_A7kOCTyKHfSRAmDkG67aDprf8UYUYHYZFM
Mobvoi TWRP : https://twrp.me/Devices/Mobvoi/ - Personally I used the C2, but I noticed Pro (catfish) is also a Snapdragon 2100
Lemme know how it goes for you. I might make a post so any interested devs get into it.
Also it's WearOS update H
Click to expand...
Click to collapse
there are 2 folders in the 7z which one is the right one? one is bigger then the other

Could anyone get the stock rom working with s2??

Bidyadhar said:
Could anyone get the stock rom working with s2??
Click to expand...
Click to collapse
I believe they are the exact same. I'd suggest do a backup of your S2 with a TWRP and then maybe flash my E2 Backup.
TWRP I used was the C2's tho

lordsolrac2 said:
I believe they are the exact same. I'd suggest do a backup of your S2 with a TWRP and then maybe flash my E2 Backup.
TWRP I used was the C2's tho
Click to expand...
Click to collapse
Hi, thanks for the backup files. Can you please let me know how do I use your E2 backup to flash my watch? I tried adb but it seems it needs .ab file to restore. And none of the TWRP works for S2.

Can anyone please share their latest Ticwatch s2/e2 backup of twrp/adb of latest firmware

alexxliu said:
Hi, thanks for the backup files. Can you please let me know how do I use your E2 backup to flash my watch? I tried adb but it seems it needs .ab file to restore. And none of the TWRP works for S2.
Click to expand...
Click to collapse
Awfully late reply and I apologize but; I suggest you take a look at this;
https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013
And check in the downloads, they have the STOCK as well as a CUSTOM rom for the E2 (again, should be 100% Compatible with S2) but also has a TWRP Build.
To answer your question; I'd suggest grabbing the TWRP for the E2 and boot into it, push my backup (or the stock or custom rom from the link above), and then make a backup of yours, and then flash the backup or rom; clear data and cache and reboot

**PERSIST REQUEST** Enrollment Problem

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.

Wifi/bluetooth keep trying to turn on but fail everytime.

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

Question Request: Persist.img

I actually found out what's the problem with my fingerprint sensor. The old owner of the phone have messed up the persit partition.
Now i haven't understand if the persist i found on this forum for the os 1.1.7 is good to flash on my phone with os 1.5.4.
If the answer is not, can someone provide me a backup? My brain is burning, i've have searched all the internet for this file
I can provide my persist, but i don't think it will be usefull
This is my Persist.img

Afaik persist stays the same. No matter what nos version you are using. Cant guarantee that someone elses persist works for you but you can try.
Drunkdos said:
I actually found out what's the problem with my fingerprint sensor. The old owner of the phone have messed up the persit partition.
Now i haven't understand if the persist i found on this forum for the os 1.1.7 is good to flash on my phone with os 1.5.4.
If the answer is not, can someone provide me a backup? My brain is burning, i've have searched all the internet for this file
I can provide my persist, but i don't think it will be usefull
This is my Persist.img
Click to expand...
Click to collapse

Please don't flash persist unless you really know the consequences! Cause persist contains wideline L1 certificates.

solomon.rajan said:
Please don't flash persist unless you really know the consequences! Cause persist contains wideline L1 certificates.
Click to expand...
Click to collapse
Yeah i know. Thats why i said that risk is from users end. With oneplus this was nightmare..