Database Info

Added line to build.prop....now bricked?

So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running

S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?

Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?

Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things

S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need

Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?

S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?

Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.

Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.

Issue with OOS flashing in TWRP

Hello,
I did a factory reset of OnePlus 8, and I also wiped the system partition. Now the only thing left on my phone is TWRP. I'd like to flash OxygenOS, so I downloaded a signed flashable zip on this thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233
But when I flash it with TWRP, it says (in blue)
"flashing A/B zip to inactive slot : A"
Step 1/2
and it's been like this for quite some time now. I wonder if I've done something wrong ? Or should I wait ?
Thanks !

up

LucasDupuis32 said:
Hello,
I did a factory reset of OnePlus 8, and I also wiped the system partition. Now the only thing left on my phone is TWRP. I'd like to flash OxygenOS, so I downloaded a signed flashable zip on this thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233
But when I flash it with TWRP, it says (in blue)
"flashing A/B zip to inactive slot : A"
Step 1/2
and it's been like this for quite some time now. I wonder if I've done something wrong ? Or should I wait ?
Thanks !
Click to expand...
Click to collapse
It should take since time but I would say no more than ten to fifteen minutes to complete. Unfortunately I don't want you to stop the process now that it's started that could definitely render it inoperable.
If it does come out of it with an error then just try again but be careful and make sure your can MSM your phone to previous version. I did my TMO to Global flash through zip file with the run all bat. That was pretty damn easy. Happy modding!

Nathan.7118391 said:
It should take since time but I would say no more than ten to fifteen minutes to complete. Unfortunately I don't want you to stop the process now that it's started that could definitely render it inoperable.
If it does come out of it with an error then just try again but be careful and make sure your can MSM your phone to previous version. I did my TMO to Global flash through zip file with the run all bat. That was pretty damn easy. Happy modding!
Click to expand...
Click to collapse
Thanks for your reply.
I left it for more than an hour and it was still on step 1/2. So I stopped the process by rebooting with ADB. When I did that it wiped my /sdcard. I tried to flash OOS again but same result ... I've never heard of MSM before. I just googled it and I see that's it's an unbrick tool only available for Windows but I'm using a Mac. I can still use my brother's laptop which runs Windows 10 but I'd like to know if there's any alternative before doing that.
I really just want to get OOS back Not crossflashing or downgrading
Thanks !

I had a same problem few days ago.
I managed to save my phone with this restore tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
Now everything works fine.

miimaa said:
I had a same problem few days ago.
I managed to save my phone with this restore tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
Now everything works fine.
Click to expand...
Click to collapse
Thank you for your answer.
I'm trying to run MSM tool but I can't boot in EDL mode and the link for the Qualcomm drivers appears to be dead ...

LucasDupuis32 said:
Thank you for your answer.
I'm trying to run MSM tool but I can't boot in EDL mode and the link for the Qualcomm drivers appears to be dead ...
Click to expand...
Click to collapse
I followed this video and it helped me to solve the problem.
I had problems with EDL-mode too. Try the EDL-mode by just pressing the volume up button and use the phones own cable.
Here's link for drivers: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043

miimaa said:
I followed this video and it helped me to solve the problem.
I had problems with EDL-mode too. Try the EDL-mode by just pressing the volume up button and use the phones own cable.
Here's link for drivers: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
Click to expand...
Click to collapse
Could you also give me the link for the video ? Thanks !

LucasDupuis32 said:
Could you also give me the link for the video ? Thanks !
Click to expand...
Click to collapse
Oops, sorry, here's the link: https://www.youtube.com/watch?v=jtc7EhNsfPA

ADB and 8T

Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R

Try nother USB C cable. Some not able to handle data.

rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!

Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!

Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R

Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.

BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??

Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.

BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!

Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11

BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,

Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".

BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,

Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!

Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R

Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.

BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone

ONEPLUS 8 STUCK W/O Software

Hello,
I have a Oneplus 8 5W from Verizon, and I followed a topic to unlock the device which I did successfully. However, I'm stuck in Fastboot. I tried installing TWRP, but couldn't utilize it to flash to software. Can someone help?

You should have used MSMTool to get a clean build of Android 11 prior to doing the unlock process. Repeat the instructions again.

Xryphon said:
You should have used MSMTool to get a clean build of Android 11 prior to doing the unlock process. Repeat the instructions again.
Click to expand...
Click to collapse
While doing that. I found out that I have made a mistake and installed Oneplus 8 Pro software into my Oneplus 8. I knew that by installing TWRP and going to the terminal where it shows the name of the device. What can I do?

SkyMine said:
While doing that. I found out that I have made a mistake and installed Oneplus 8 Pro software into my Oneplus 8. I knew that by installing TWRP and going to the terminal where it shows the name of the device. What can I do?
Click to expand...
Click to collapse
Again, use the MSMTool if still possible to restore to the original partitions. Start from the beginning again; your partitions are already messed up enough.

Xryphon said:
Again, use the MSMTool if still possible to restore to the original partitions. Start from the beginning again; your partitions are already messed up enough.
Click to expand...
Click to collapse
I get an error, "Device does not match image"

SkyMine said:
I get an error, "Device does not match image"
Click to expand...
Click to collapse
Use the stock. ops from the OnePlus 8 5G UW bootloader unlock page.
As stated before, please read the instructions thoroughly.

Xryphon said:
Use the stock. ops from the OnePlus 8 5G UW bootloader unlock page.
As stated before, please read the instructions thoroughly.
Click to expand...
Click to collapse
Thank you very much, I just used the stock.ops and then after that, I used the unlock.ops, I booted directly to TWRP, and it still says "Oneplus 8 Pro". What do you advise me to do next?

SkyMine said:
Thank you very much, I just used the stock.ops and then after that, I used the unlock.ops, I booted directly to TWRP, and it still says "Oneplus 8 Pro". What do you advise me to do next?
Click to expand...
Click to collapse
I believe the TWRP is engineered to be cross - device compatible. You can use it as normal, provided that it is working.

Xryphon said:
I believe the TWRP is engineered to be cross - device compatible. You can use it as normal, provided that it is working.
Click to expand...
Click to collapse
The only problem right now is that I'm stuck in 8 pro software, and my phone is Oneplus 8. I have no idea how this has happened, I was very tired and working so it slipped my mind to double-check. I'm not sure how to go back to Oneplus 8 software..
I want to thank you for being patient with me!

i ended up in a Qualcomm crashdump mode lol I'm so done with this device....

OnePlus 8 TMO Missing IMEI and can't unlock bootloader

Hey yall, I really need some help.
So some back story:
I started using a oneplus 8 TMO version and wanted to unlock the bootloader to get android 12 and root the phone. So I went through the process of getting an unlock token and when I finally got it, unlocked my bootloader, flashed the global version of oxygen os, and got it updated to android 12. Everything was working great. So then I wanted to root the phone so I downloaded twrp, booted into fastboot, and tried flashing it. The phone then booted into the system even though I told it to boot into recovery. After about a minute or so it froze and rebooted into a kernal panic. I unfortunately do not have what it said and cant repeat the process, but it booted into recovery and I clicked reason for boot and it said something about the kernal. So after a reboot it then went into crash dump mode. So I had to use the msm download tool (unfortunately I only had the tmo msm version and thought I could just repeat the process because I had slow internet and didnt want to download the global msm tool) to get the phone working again. So booted into edl mode, reflashed the phone, and it booted up. The problem now is that I do not have an IMEI number. I have a wifi address, bt address, and everything else that makes me assume that the efs partition is still ok (but I dont know enough to debate that) but it does not recognize my sim card. The phone also freezed and restarts approximately every 30 seconds.
And now my problem and what I have tried:
Because I have no IMEI I cannot enable oem unlocking in developer settings, cant flash anything in the bootloader - including the unlock token - and can barely do anything in the system because it only stays on for small amounts of time. I have tried many imei write tools such as qualcomm smartphone write imei, readnwrite tool, fastboot imei writer, miracle box, and I think some others but none of them recognize my phone. Ive also tried the oneplus debloat and oem unlock script to try and bypass the setting but it didnt do anything. I have dialed *#801# and was able to enable engineering mode and diag toggle but it still didnt do anything for me. So I really dont know what to do any more. When in the bootloader or recovery the phone does not reboot, so I can stay there as long as I need. Any help on this would be greatly, greatly, greatly appreciated.

Have you tried using the MSMTool again?

Xryphon said:
Have you tried using the MSMTool again?
Click to expand...
Click to collapse
Yeah unfortunately that hasn't worked... I've done it miltiple times with the T-Mobile one and can't use any other one because I don't have an unlocked bootloader... If I had a way to bypass the oem unlocking option in the settings then I might have a chance to fix it but don't know how to do that...

try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen

gingerboy92 said:
try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen
Click to expand...
Click to collapse
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.

shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out

gingerboy92 said:
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out
Click to expand...
Click to collapse
Yeah, OOS 12 messed up my phone for a bit until I was able to get OOS 11 back on both slots.

shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
which worked for you?