Related
I own a moto x style (XT1572) (DUAL SIM) and have a problem regarding my IMEI number gone null
I did wait for a long time to receive nougat 7.0 update on my device but since I could'nt resist i went for flashing my device
after i unlocked my bootloader i flashed super su zip which unfortunately was a BETA version and hence my device got caught up in a boot loop.
To avoid wasting my time i searched for a restock tool and immediately flashed it.
It was 5.1.1 stock but for XT1575 *post the flash thing* my sim was not detected (both the sim cards).
i went on searching for the problem and found out that both IMEI and BASEBAND version was null and unknown respectively.
Till now i have downloaded lots of recovery patches and boot images including all other stuff but no positive result.
never ever this happened while flashing a device until with this one.
i hope you guys will help me ?
why don't you download the right one for XT1572?!
downloading and flashing wrong firmware cause issues like you are having now, try downloading the right firmware and flash it with that stock tool you used before.
I did but could not get a stock tool for XT1572
Will I get my IMEI number back after flashing the correct firmware?
When the phone is switched on it shows XT1575 on PC where as it shows XT1572 on PC in recovery mode
kash909 said:
I did but could not get a stock tool for XT1572
Will I get my IMEI number back after flashing the correct firmware?
When the phone is switched on it shows XT1575 on PC where as it shows XT1572 on PC in recovery mode
Click to expand...
Click to collapse
yes you probably will get it back after flashing the correct firmware.
After i updated the Firmware of my Moto Z XT 1650-03 i cant use Wifi and Bluetooth anymore and my MAC Adress is bit funny 02:00:00:00:00:00 .
I tried to flash a Firmware through RSD Lite but im getting the Error gpt validation failed.
After i removed the string in the .xml file the software is working till flashing boot.img and than i get the Error Phone Retourned Error.
What can i do ?
dubist said:
After i updated the Firmware of my Moto Z XT 1650-03 i cant use Wifi and Bluetooth anymore and my MAC Adress is bit funny 02:00:00:00:00:00 .
I tried to flash a Firmware through RSD Lite but im getting the Error gpt validation failed.
After i removed the string in the .xml file the software is working till flashing boot.img and than i get the Error Phone Retourned Error.
What can i do ?
Click to expand...
Click to collapse
So unhappy you!
Same here, i give to Moto warranty but they said need replace motherboard with more 400USD, and i taked it back.
Now bought oneplus 5 for replacement, it much better, can root, flash, upgrate any rom, kernel ... freely no problem.
Will never buy any Lenovo.
dubist said:
After i updated the Firmware of my Moto Z XT 1650-03 i cant use Wifi and Bluetooth anymore and my MAC Adress is bit funny 02:00:00:00:00:00 .
I tried to flash a Firmware through RSD Lite but im getting the Error gpt validation failed.
After i removed the string in the .xml file the software is working till flashing boot.img and than i get the Error Phone Retourned Error.
What can i do ?
Click to expand...
Click to collapse
I noticed the same thing with the wifi MAC when I flashed ElementalX kernel to my otherwise stock but rooted Moto Z.
Restoring from my TWRP backup resolved the issue and the MAC address displays correctly again.
Is your Moto Z bootloader unlocked and do you have TWRP installed? If not, maybe you can go down that route to flash a custom ROM. (unfortunately I don't think the official firmware is available)
no my Bootloader is still locked.
No possibility?
If your bootloader ia still locked, you probably still have warranty.
Contact lenovo for that, they are your best bet.
Byte_76 said:
I noticed the same thing with the wifi MAC when I flashed ElementalX kernel to my otherwise stock but rooted Moto Z.
Restoring from my TWRP backup resolved the issue and the MAC address displays correctly again.
Is your Moto Z bootloader unlocked and do you have TWRP installed? If not, maybe you can go down that route to flash a custom ROM. (unfortunately I don't think the official firmware is available)
Click to expand...
Click to collapse
Can you share your backup TWRP ROM?
Tks!
Can I get copy of the correct rom from someone. Received a phone with the wrong one and don't have a backup to return to. Thanks.
I have the same issue. This happened after I tried flashing back the previous build on my Moto Z force. It flashed some partitions, but failed for the rest (For obvious reasons), so I need to figure out which partition has a mismatch and put it back to 7.1.1... Problem is, I need a full firmware to do this and it's not available online yet.
I'm pretty sure from my experience that it's just the modem which needs flashing. If someone is running a Moto Z unlocked on 7.1.1, can you do this in ADB in root and run the following command:
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin
Then upload the modem somewhere for us?
karendar said:
I'm pretty sure from my experience that it's just the modem which needs flashing. If someone is running a Moto Z unlocked on 7.1.1, can you do this in ADB in root and run the following command:
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin
Then upload the modem somewhere for us?
Click to expand...
Click to collapse
I think that this modem will work
https://www.androidfilehost.com/?fid=889764386195921696
It is for 7.1.1 stock
Download and extract then
fastboot flash modem NON-HLOS.bin
lollyjay said:
I think that this modem will work
https://www.androidfilehost.com/?fid=889764386195921696
It is for 7.1.1 stock
Download and extract then
fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
You my friend, just saved my phone. Wifi and BT is back. Thanks a million!
@Op, boot to safe mode:
Turn off phone
Hold vol down + Power
Connect phone to PC
Make sure fastboot is properly installed
fastboot flash modem NON-HLOS.bin
Reboot phone
Wifi and BT will be back up and running.
karendar said:
You my friend, just saved my phone. Wifi and BT is back. Thanks a million!
@Op, boot to safe mode:
Turn off phone
Hold vol down + Power
Connect phone to PC
Make sure fastboot is properly installed
fastboot flash modem NON-HLOS.bin
Reboot phone
Wifi and BT will be back up and running.
Click to expand...
Click to collapse
Glad I could help. The modem zip was prepared by erfan.
lollyjay said:
Glad I could help. The modem zip was prepared by erfan.
Click to expand...
Click to collapse
Hi,
I've got the same Problem with WLan MAC 02:00:00:00:00:00 after updating.
I download the NON-HLOS.bin file.
but it is for 7.1.1 can i still use it?
I followed these steps:
-> Turn off phone (check)
-> Hold vol down + Power (check)
-> Connect phone to PC (check)
-> Make sure fastboot is properly installed (Fastboot? Ok, i am downloading the Adroid Studio with fastboot)
-> fastboot flash modem NON-HLOS.bin (check not yet)
-> Reboot phone (check not yet)
-----
wlan mac: 02:00:00:00:00:00
Android 7.0
Baseband_Version: M8996_1239.53.01.126R SRS
Build-Nummer: NPLS25.86-31-5
reteu
-----
I don't have any backup or experience with these things
A my phone is unrooted.
What does this line on the bootscreen mean -> "AP Fastboot Flash Mode (secure)"
These situation is just a little bit overwhelmed for me
minotaurus81 said:
Hi,
I've got the same Problem with WLan MAC 02:00:00:00:00:00 after updating.
I download the NON-HLOS.bin file.
but it is for 7.1.1 can i still use it?
I followed these steps:
-> Turn off phone (check)
-> Hold vol down + Power (check)
-> Connect phone to PC (check)
-> Make sure fastboot is properly installed (Fastboot? Ok, i am downloading the Adroid Studio with fastboot)
-> fastboot flash modem NON-HLOS.bin (check not yet)
-> Reboot phone (check not yet)
-----
wlan mac: 02:00:00:00:00:00
Android 7.0
Baseband_Version: M8996_1239.53.01.126R SRS
Build-Nummer: NPLS25.86-31-5
reteu
-----
I don't have any backup or experience with these things
A my phone is unrooted.
What does this line on the bootscreen mean -> "AP Fastboot Flash Mode (secure)"
These situation is just a little bit overwhelmed for me
Click to expand...
Click to collapse
This works only for phone with unlocked bootloader.
lollyjay said:
This works only for phone with unlocked bootloader.
Click to expand...
Click to collapse
Ah ok thank you
is there any other Option to fix this problem without unlocking it? (have my phone now for 1.5 months).
Yes i know i have guarantee
If i unlock it is there any fool-proof tutorial?
minotaurus81 said:
Ah ok thank you
is there any other Option to fix this problem without unlocking it? (have my phone now for 1.5 months).
Yes i know i have guarantee
If i unlock it is there any fool-proof tutorial?
Click to expand...
Click to collapse
I am not aware of any solution other than wait for the next OTA.
As long as you know that your warranty is void after unlocking the bootloader, the procedure is well detailed on the Motorola website.
lollyjay said:
This works only for phone with unlocked bootloader.
Click to expand...
Click to collapse
No, that's not true. Flashing the GPT, the bootloader, the modem partition, the BT partition and DSP partition works fine in a locked bootloader phone. The only partitions that can't be flashed in a locked bootloader status is system, recovery and boot.
His issue is not the same as mine though, as mine occurred when I attempted to roll back to 7.0. He seems stuck on 7.0. So he would need the proper NON-HLOS.bin for his version and flash it.
@minotaurus81 did you update your phone to 7.1.1 and did it fail? Because that's the only way I think it could have messed up your phone. I strongly suggest that if you don't have the technical knowledge to fix this to return your phone for warranty repair. You might mess things up even further if you don't do the right thing...
lollyjay said:
I am not aware of any solution other than wait for the next OTA.
As long as you know that your warranty is void after unlocking the bootloader, the procedure is well detailed on the Motorola website.
Click to expand...
Click to collapse
Just to clarify, waiting for next OTA might not solve anything. OTA packages usually have .p (patch) files instead of the entire file to update with in order to save space. If it detects that a different modem is flashed on the device, it will simply fail and not flash anything else.
Hey guys,
my phone has the same issue. I tried to flash the modem but that did not work, still no Wifi and Bluetooth. I did not unlock my phone yet since karendar stated there was no need for that.
My phone got wet a couple of months ago (which is why there is no warranty anymore) but it worked fine until I updated to 7.1.1 recently. So I'm pretty sure the issue is due to the update.
This is what happened when flashing the modem:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (81729 KB)...
OKAY [ 1.766s]
writing 'modem'...
OKAY [ 1.110s]
finished. total time: 2.892s
Does that look alright or should I unlock my phone and try again?
Thanks for your help
I have the same issue, but at least i have WiFi. Bluetooth not working anymore after 7.1.1. Tried everiything !!!!
Enviado desde mi XT1650-03 mediante Tapatalk
Hi guys,
After reading through many of the different guides here regarding how to enable different LTE bands (band 20 I'm interested in) I decided to give it a go on my new Note 4.
After some tinkering with the binary values etc from this guide here: https://forum.xda-developers.com/redmi-note/general/unlock-lte-bands-step-step-xiaomi-mi-t3084774
It did not seem to do anything since band 20 in the place I live is usually not that strong signal wise compared to band 3 and 7.
So I thought: "Yeah, I'll just disable the other 2 and see if the band 20 works". This was unsuccessful and after some more tinkering I managed to completely lock out the whole LTE functionality of my phone.
Even inserting the decimal value from before I started this is working.
Any ideas on how to do a reset of the LTE part of the modem? Tried flashing an updated baseband, but to no avail.
Try doing
Code:
fastboot erase modemst1
fastboot erase modemst2
and then flash following this guide.
Attention when flashing with MiFlash: in the lower part of the window you can choose different .bat files, choose the flash_factory.bat (or flash_all.bat if flash_factory.bat won't work). Don't choose any .bat with lock in the name or you'll re-lock the bootloader.
Hi,
Tried to erase the modems, but I'm getting "Error: This image isn't allow download) error.
Any tips on how to get that to work? Tried using the old Google trick, but did not find a good solution for that.
I got that error too while flashing the FSG partition in flash_factory.bat but I didn't investigate on the problem, just used another flash.bat.
I searched for this error, looks like it's present only on recent devices (Redmi Note 4 and Redmi 4 variants). Maybe it's a new kind of protection, some partitions become read-only when we unlock the bootloader, to preserve the phone functionality?
If that's the case, first flash flash_all_lock.bat, that will flash the MIUI ROM and relock the bootloader (possibly unlocking the protected partitions), then re-flash the same ROM but using the flash_factory.bat (that contains a couple of flashing commands not present in the other .bat files, including the erase modemst commands).
Then, you can also try flashing via fastboot also the persist.img, just to be sure
Code:
fastboot flash persist persist.img
(this is not present in any .bat file)
At last check if the phone is working, and then you can unlock the bootloader easily, without any wait.
EDIT: I'm wrong, you cannot use fastboot to flash when the bootloader is locked (even if the images are original from Xiaomi).
Only solution I can think about now is, while the bootloader is unlocked, you can try to access the blocked partitions with other tools like Flashify (like you did while damaging them).
Managed to get it working again, with a separate xqcn backup which I modded with the IMEI numbers from my own phone
Juji said:
Managed to get it working again, with a separate xqcn backup which I modded with the IMEI numbers from my own phone
Click to expand...
Click to collapse
Can you link to the qcn file? I'm facing a similar problem and I would need that file.
Excuse my beginner English.
Here you go: http://en.miui.com/thread-545300-1-1.html
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?
Check your OnePlus updater.
mingkee said:
Check your OnePlus updater.
Click to expand...
Click to collapse
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
S build based on Color OS and even the font changed.
I think I can deal with mine, but the most important of all, there's no player error on rooted N200 with S
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
The12thJuror said:
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
Click to expand...
Click to collapse
Yeah, I called OP three times got the same promise from OPs customer service and they never got back with me. I've never dealt with a less enthusiastic company when dealing with a serious product defect. The tech support people at first acted like the didn't believe me when I described the problem. Then once I had (I think) convinced them the problem was real, their response was like "oh well, too bad, so sad". OP offered no solutions or even ideas of what to try to do to fix the problem.
Do they test anything before pushing out an update?
I had a two day window left for returning the devices for a refund so now they're gone, and I'm gone as an OP customer, I can't just do without a phone while they fumble around trying to figure out the details for some (maybe) upcoming patch.
Good devices, terrible customer service. Never settle, nope, never again.
Scragge said:
According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
Try this
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Travisholt92 said:
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Click to expand...
Click to collapse
Do you know where to download the A12(or at least the latest A11 update so I can update to A12 via OTA) stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Tyreethetruth said:
Do you know where to download the A12 stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Click to expand...
Click to collapse
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Travisholt92 said:
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Click to expand...
Click to collapse
Thank you! I been stuck on the same update like 4-5 updates ago
On this build (metro/TMobile version converted. I can't keep android auto connected. I went into developer options and selected the default to transfer files/ android auto and all the other options but it just connects for a few and then disconnected and says device unsupported.
Rooted device and using a alpine iLX-w650
Tyreethetruth said:
Thank you! I been stuck on the same update like 4-5 updates ago
Click to expand...
Click to collapse
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Travisholt92 said:
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Click to expand...
Click to collapse
So I get on computer and go on bootloader and type "adb logcat"?
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Travisholt92 said:
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Click to expand...
Click to collapse
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Tyreethetruth said:
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Click to expand...
Click to collapse
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Travisholt92 said:
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Click to expand...
Click to collapse
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Tyreethetruth said:
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Click to expand...
Click to collapse
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Travisholt92 said:
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Click to expand...
Click to collapse
Gotcha, one last thing how do I flash using fastboot enhance? Idk what to pick to flash the A12 OTA
EDIT: Nvm I extracted the update and found the payload
Magisk patched boot.img for this release: https://drive.google.com/file/d/1A2x8YbnnO6SJq-R-1rdZZ18CU673Z2-Y/view?usp=sharing