Database Info

Beta program

Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards

You can download the full image here

I dont have oem unlocked. I can sideloade it?

Yea even i didn't get it. I guess it not for the verizon phones.

Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....

Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.

I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.

I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.

k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks

Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?

farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.

If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk

joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?

murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.

murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk

joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat

OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi

murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk

I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.

joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app

Verizon Pixel -- I screwed up

Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
The problem is I sideloaded the J series rom by mistake, and not the E series rom. The J series is the euro spec version
I tried to correct it by reflashing the E series but I received an error that the timestamp on the OTA was sooner than the J series and downgrading was not allowed
Does anyone have a download link to the Verizon specific OTA file for 7.1.2 so I can attempt to flash and correct???
Is the only other fix trying to do a full system reimage or the previous 7.1.1 build ??
Thanks
Sent from my Pixel using Tapatalk

Joe92T said:
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
The problem is I sideloaded the J series rom by mistake, and not the E series rom. The J series is the euro spec version
I tried to correct it by reflashing the E series but I received an error that the timestamp on the OTA was sooner than the J series and downgrading was not allowed
Does anyone have a download link to the Verizon specific OTA file for 7.1.2 so I can attempt to flash and correct???
Is the only other fix trying to do a full system reimage or the previous 7.1.1 build ??
Thanks
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Use the full E image and take out the -w from flash-all.bat so you don't wipe SD.
Sent from my Pixel using XDA-Developers Legacy app

That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Sent from my Pixel using Tapatalk

Joe92T said:
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Click to expand...
Click to collapse
I currently have N2G47E on my Verizon purchased Pixel now. No issues that I've run into.

Joe92T said:
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Use E. The new VZW firmware isn't on Google's site. I flashed E and all is just fine.
Sent from my Pixel using XDA-Developers Legacy app

Joe92T said:
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
Click to expand...
Click to collapse
Are you bootloader unlocked?

No
Sent from my Pixel using Tapatalk

So I tried to flash the stock Google firmware for the E build and got told no due to locked bootloader... I can't even flash official images?
Sent from my Pixel using Tapatalk

Joe92T said:
So I tried to flash the stock Google firmware for the E build and got told no due to locked bootloader... I can't even flash official images?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Not with a locked bootloader.
Sent from my Pixel using XDA-Developers Legacy app

So the only option I have is to find ota packages with a older timestamp?
Sent from my Pixel using Tapatalk

Joe92T said:
So the only option I have is to find ota packages with a older timestamp?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If it is running fine on J then why not wait until May and sideload or take the OTA then.
I'm hearing there is a known Verizon issue with Volte on the K build anyway.
Sent from my Pixel using XDA-Developers Legacy app

I really wish I could factory flash the entire new image. I almost feel like I've "corrupted" it by installing this incorrect OTA and that even if I flash a new ota going forward that there may be some old lingering stuff kicking around from this old one
Sent from my Pixel using Tapatalk

Joe92T said:
I really wish I could factory flash the entire new image. I almost feel like I've "corrupted" it by installing this incorrect OTA and that even if I flash a new ota going forward that there may be some old lingering stuff kicking around from this old one
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing is corrupted, relax. Wait for the OTA next time and then factory reset it if that will ease your mind. But it's really not necessary the phone is fine. You might be able to sign up for the beta, it will wipe the device, then roll back with another wipe and accept the OTA when it arrives. Probably more trouble than it's worth.
Sent from my Pixel using XDA-Developers Legacy app

Protibus said:
Use the full E image and take out the -w from flash-all.bat so you don't wipe SD.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay, this one caught my eye. The OP, like me, has a Verizon Pixel. So my phone's bootloader is locked until someone finds an appropriate exploit and publishes it, if ever. And I also sideloaded the N2G47J image by mistake, didn't know it was Deutsche Telekom, thought it was just the latest *sigh*. Learned my lesson about doing research.
After sideloading N2G47J, I did try to sideload the N2G47E image, and that failed because the E image is earlier than the J image, and it won't let me flash an earlier image (bootloader locked).
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Otherwise I'll have to wait for next month's update to get my phone working right again. At the moment, it has the "Wi-Fi calling" setting set to "Cellular preferred", which causes the phone to use up a lot of battery trying to make a low cellular signal work. When I've had "Wi-Fi calling" set to "Wi-Fi preferred", that doesn't happen since if you prefer Wi-Fi calling, apparently the phone doesn't care about the cell signal as long as you're on Wi-Fi. So at home, I have to set it on Airplane mode and turn Wi-Fi back on to keep my battery from getting drained too quickly. I'm anxious to get this problem fixed, since I forget to turn Airplane mode off when I leave the house and miss calls and texts.
Thanks!

RogerSC said:
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Click to expand...
Click to collapse
No you can not do that, you are bootloader locked.

RogerSC said:
Okay, this one caught my eye. The OP, like me, has a Verizon Pixel. So my phone's bootloader is locked until someone finds an appropriate exploit and publishes it, if ever. And I also sideloaded the N2G47J image by mistake, didn't know it was Deutsche Telekom, thought it was just the latest *sigh*. Learned my lesson about doing research.
After sideloading N2G47J, I did try to sideload the N2G47E image, and that failed because the E image is earlier than the J image, and it won't let me flash an earlier image (bootloader locked).
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Otherwise I'll have to wait for next month's update to get my phone working right again. At the moment, it has the "Wi-Fi calling" setting set to "Cellular preferred", which causes the phone to use up a lot of battery trying to make a low cellular signal work. When I've had "Wi-Fi calling" set to "Wi-Fi preferred", that doesn't happen since if you prefer Wi-Fi calling, apparently the phone doesn't care about the cell signal as long as you're on Wi-Fi. So at home, I have to set it on Airplane mode and turn Wi-Fi back on to keep my battery from getting drained too quickly. I'm anxious to get this problem fixed, since I forget to turn Airplane mode off when I leave the house and miss calls and texts.
Thanks!
Click to expand...
Click to collapse
You cannot flash a full image with a locked bootloader, must be unlocked. With a locked bootloader you are only able to sideload an OTA using ADB.
Sent from my Pixel using XDA-Developers Legacy app

Protibus said:
You cannot flash a full image with a locked bootloader, must be unlocked. With a locked bootloader you are only able to sideload an OTA using ADB.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, that's what I did, adb sideloaded the J OTA that I downloaded from the Google Android Developers site: https://developers.google.com/android/ota . From what the OP said, that's what they did, too. And then adb sideloading the E OTA on top of that failed, since it is an earlier OTA. So I'm currently looking for a solution for getting the E update on my phone.
So you're not talking about using adb sideload, then, like the OP was? I'm totally confused, what were you suggesting to the OP that he do to be able to get the E image on a Verizon Pixel that already had the J image? I guess that I'm not following how I can do this with a locked bootloader? I'd love to get a clue how this could be done? Doesn't matter to me how much work it is, I'm open to learning about how to do this, and gathering whatever tools I would need?
It just occurred to me, were you assuming that the OP has an unlocked bootloader, then? I made the opposite assumption I guess, since they were using adb sideload in the first place
Thanks!

RogerSC said:
Yes, that's what I did, adb sideloaded the J OTA that I downloaded from the Google Android Developers site: https://developers.google.com/android/ota . And then adb sideloading the E OTA on top of that failed, since it is an earlier OTA. So I'm currently looking for a solution for getting the E update on my phone.
So you're not talking about using adb sideload, then? I'm totally confused, what were you suggesting to the OP that he do to be able to get the E image on a Verizon Pixel that already had the J image? I guess that I'm not following how I can do this with a locked bootloader? I'd love to get a clue how this could be done? Doesn't matter to me how much work it is, I'm open to learning about how to do this, and gathering whatever tools I would need?
Thanks!
Click to expand...
Click to collapse
Sideloading an OTA you use ADB, bootloader does not have to be unlocked. Flashing a full image, you use Fastboot which requires an unlocked bootloader. The beauty of having an unlocked bootloader is if you mess up it gives you the ability to flash a full image to put you back to some full stock condition.
Sent from my Pixel using XDA-Developers Legacy app

I would bet that the Verizon OTA has a later timestamp then both of the Google official images. So we should be able to flash that to fix it over E or J
The problem is I can't find a download link to the Verizon OTA anywhere at all. No one has it
Sent from my Pixel using Tapatalk

Joe92T said:
I would bet that the Verizon OTA has a later timestamp then both of the Google official images. So we should be able to flash that to fix it over E or J
The problem is I can't find a download link to the Verizon OTA anywhere at all. No one has it
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I would try it if I had a copy of it.
Sent from my Pixel using XDA-Developers Legacy app

Is it possible to root on 9.5.8 yet?

I never rooted my oneplus 7 pro before and I recently updated to OOS 9.5.8, is there a way to root on this version yet?

Yes it's just like all the others

You can definitely root it. I have a T-Mobile version, converted to the international version, have the latest version of Oxygen, and root my device. I definitely suggest that you go through the root process first. I'm at work right now so I'm typing fast so I could get off before I get caught....lol

JodyBreeze901 said:
You can definitely root it. I have a T-Mobile version, converted to the international version, have the latest version of Oxygen, and root my device. I definitely suggest that you go through the root process first. I'm at work right now so I'm typing fast so I could get off before I get caught....lol
Click to expand...
Click to collapse
I have the European version (GM1913), what's the most appropriate guide?
Try not to get caught!

oneplus7prouser said:
I have the European version (GM1913), what's the most appropriate guide?
Try not to get caught!
Click to expand...
Click to collapse
Download the All In One Tool: https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993
Install drivers from within the tool.
Unlock Bootloader within the Tool App If you can't go here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-edition)
Unlocking Bootloader will reset your phone to factory and erase data so make a backup if you care to save anything.
Flash Twrp Recovery within the TOOL App. You can also do it manually by going here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Download and flash Magisk from here: https://******************/magisk-beta
Reboot to system.

JodyBreeze901 said:
You can definitely root it. I have a T-Mobile version, converted to the international version, have the latest version of Oxygen, and root my device. I definitely suggest that you go through the root process first. I'm at work right now so I'm typing fast so I could get off before I get caught....lol
Click to expand...
Click to collapse
Any benefit to the root? Haven't seen anything that really made me want to do it. What did you do with root?
Sent from my GM1915 using Tapatalk

GlitchMob said:
Any benefit to the root? Haven't seen anything that really made me want to do it. What did you do with root?
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Honestly, I only did it for two reasons.....
1. Viper4Android (I listen to music ALOT)
2. AdAway (I hate ads!)
Both which requires ROOT.

Help! Oneplus Newbie!

While i am no beginner when it comes to modding phones, having done so with Samsungs Sonys and my last HTC 10. But this is my first Oneplus and my first time dipping toes in the world of A/B partitions as well. My device is a 1910 GM21AA. While i have gone through the guides regarding bootloader unlocks and magisk rooting, I have failed to grasp some more basic aspects. For one thing, i seem to have the Chinese variant but mine isnt Hydrogen OS, i am currently sitting on 9.5.3 OOS. I was wondering how i could perhaps shift to the Global firmware. Am i to take the latest 9.5.11 OTA from https://forum.xda-developers.com/on...7-pro-global-repo-oxygen-os-t3930585#poststop and simply put it in the download folder and do a local update from the system update on the phone? Thanks in advance

Use the oygen os updater from the play store download full rom which is around 2gb and do local upgrade.
FYI GM21AA is Indian Version
Sent from my GM1911 using Tapatalk

zmafreak said:
Use the oygen os updater from the play store download full rom which is around 2gb and do local upgrade.
FYI GM21AA is Indian Version
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
the packages shown in the app seem to be the same zips in the thread i linked...so all i do is take the GM21AA from the thread and just do a local update? I read that 1910 is the Chinese variant for my device but it has this GM21AA build which just made things so confusing. Thank you.

I would now like to know of things i can do to bring my OP7Pro to life in case something ever goes wrong with Local storage updates or just Fcked up in general

linx1287 said:
the packages shown in the app seem to be the same zips in the thread i linked...so all i do is take the GM21AA from the thread and just do a local update? I read that 1910 is the Chinese variant for my device but it has this GM21AA build which just made things so confusing. Thank you.
Click to expand...
Click to collapse
That should do.. it should give you an error if the update is incompatible. Incase you mess up you can always fastboot and update using this thread https://www.google.co.in/amp/s/foru...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Sent from my OnePlus 7 Pro using Tapatalk

zmafreak said:
That should do.. it should give you an error if the update is incompatible. Incase you mess up you can always fastboot and update using this thread https://www.google.co.in/amp/s/foru...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Sent from my OnePlus 7 Pro using Tapatalk
Click to expand...
Click to collapse
After flashing the rom, i cant for some reason enter engineering mode. I could with my original firmware. Has this happened to you or anyone?

I never tried it tbh
Sent from my OnePlus 7 Pro using Tapatalk

linx1287 said:
After flashing the rom, i cant for some reason enter engineering mode. I could with my original firmware. Has this happened to you or anyone?
Click to expand...
Click to collapse
I could be wrong, but I think that's the norm with everyone since updating. Thinkni read it in one of the XDA forums around here somewhere.

How do i roll back to full stock if i am on custom rom? This is unfortunately also my first time dealing with A/B partitions.
Aside from these, i have been going around the forums and had a few more questions that i hope someone could help me with....
1. Whenever i come across a rom not based on OOS, i keep coming across never wiping system or vendor, why is that?
2. I come across flashing OOS a lot, how do i flash OOS when i am in a custom rom not based on OOS?
 @hallo dare @virtyx

zmafreak said:
Use the oygen os updater from the play store download full rom which is around 2gb and do local upgrade.
FYI GM21AA is Indian Version
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
GM21AA IS global too
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
hallo dare said:
I could be wrong, but I think that's the norm with everyone since updating. Thinkni read it in one of the XDA forums around here somewhere.
Click to expand...
Click to collapse
look in the volte thread
there is an apk to installnand enables it again with limited functionality
or use MSM tool to go back to 953 and tibu backup and restore on 9511
oneplus removed it for some reason...
maybe because they found out we're forcing VOLTE?

linx1287 said:
How do i roll back to full stock if i am on custom rom? This is unfortunately also my first time dealing with A/B partitions.
Aside from these, i have been going around the forums and had a few more questions that i hope someone could help me with....
1. Whenever i come across a rom not based on OOS, i keep coming across never wiping system or vendor, why is that?
2. I come across flashing OOS a lot, how do i flash OOS when i am in a custom rom not based on OOS?
@hallo dare @virtyx
Click to expand...
Click to collapse
full zip upgrade
or MSM tool.
you will be wiped.

virtyx said:
full zip upgrade
or MSM tool.
you will be wiped.
Click to expand...
Click to collapse
Do i use MSM tool or fastboot method whenever i need to get back to complete stock without any root or twrp? If so then i think MSM tool or fastboot roms would be a great way to go. 1 question, does using msm or fastboot return the phone to stock while keeping the bootloader unlocked? Also, is it ok to downgrade to a lower version of OOS with MSM or fastboot roms? i think 9.5.11 for me introduced some random background battery drain and this weird mobile data bug where switching to it doesnt enable the connection until much much later

I personally use fastboot. All you need to do is plug the phone in>Boot to fastboot (hold vol up and down and power all at once)>On the computer launch flashall.bat (dont run it as administrator, just launch it).

PerthBoi92 said:
I personally use fastboot. All you need to do is plug the phone in>Boot to fastboot (hold vol up and down and power all at once)>On the computer launch flashall.bat (dont run it as administrator, just launch it).
Click to expand...
Click to collapse
Do you use it to downgrade or whenever you need to go back to full stock after modding? does it keep the bootloader unlocked or does it relock it? Thanks. Sorry for the noob questions. This is my first Oneplus. I have kept my device stock until i get a good idea of how to deal with things going south.

I need a little guidance regarding this thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Are these rom packages for MSMtool or fastboot packages?
EDIT:
Never mind...msmtool stuff just went through the files

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?