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
Related
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Willing to pay $20 paypal or google wallet to anyone that can help me get my phone back working....
SixShots said:
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Click to expand...
Click to collapse
You should be fine, I'm assuming you flashed that boot logo without installing a custom kernel to disable force encryption and here's how I flashed stock when i did something similar.
This is exactly what I did from a bricked phone. I got a strange "error" message after flashing this that looks like the no command error, but after holding power it rebooted to Nougat.
Using Minimal adb and Fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps!
I used the Mexican Nougat firmware from here, I'm on 32GB UK model though. https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Just don't flash a MM one if you're coming from Nougat, that will not work. And remember to check the number of system chunks it may not be 16 for whichever firmware you use.
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
SixShots said:
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
Click to expand...
Click to collapse
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
supacrazyguy42 said:
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
Click to expand...
Click to collapse
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
SixShots said:
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
Click to expand...
Click to collapse
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
supacrazyguy42 said:
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
Click to expand...
Click to collapse
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
SixShots said:
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
Click to expand...
Click to collapse
Ah I don't know why that is, as i said I'm at sure what's best for your model sorry. The easy flash to Nougat guide link i sent you may be better, but yeah if you know it came with RETLA then give that one a try :good:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
D13H4RD2L1V3 said:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
Click to expand...
Click to collapse
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
SixShots said:
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
Click to expand...
Click to collapse
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
D13H4RD2L1V3 said:
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
Click to expand...
Click to collapse
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
SixShots said:
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
Click to expand...
Click to collapse
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
D13H4RD2L1V3 said:
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
Click to expand...
Click to collapse
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
SixShots said:
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
Click to expand...
Click to collapse
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
D13H4RD2L1V3 said:
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
Click to expand...
Click to collapse
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
SixShots said:
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
Click to expand...
Click to collapse
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
D13H4RD2L1V3 said:
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
Click to expand...
Click to collapse
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
SixShots said:
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
Click to expand...
Click to collapse
Well, here's the problem.
If you're on the 7.0 GPT and bootloader, you're out-of-luck. Because Moto has changed the rules on those to not accept Marshmallow-based firmware. Trying to flash a MM firmware will result in failure. Trying to downgrade the bootloader may cause your device to be F.U.B.A.R.
If you're still on the MM bootloader, just use the steps outlined earlier in the thread to flash N and then use the instructions and threads I linked to flash both the custom kernel and root access. If everything goes well, your Z should come back to life with those sweet-sweet notification shade goodness.
Hello guys,
I experienced an interesting problem the last time: every time I want to start my phone normally, it does not boot Android, it boots the Recovery (TWRP).
This does not happen when I start the bootloader and then click on "start".
This happened after I tried to (unsuccessful) flash the Oreo Soak test (can be found here: https://forum.xda-developers.com/moto-z/how-to/official-moto-z-8-0-0opl27-281978-soak-t3750151)
Also, the system clock stands on 01.01.1970, I think that's not normal at all!
I DIDN'T flash bootloader and GPT.
I already tried: fastboot oem fb_mode_set and then ffastboot oem fb_mode_clear
substitute system and every other image I flashed with the Oreo Soak test with 7.1.1 stock rom images
(Flashed: boot, system, dsp and oem)
Nothing helped so far.
Can you help me?
Or do you have an idea?
What I haven't tried so far is flashing stock rom with december security patch, maybe someone can send me a flashable version?
EDIT:
I managed to fix the strange boot behavor.
Same problem?
How I fixed it:
reflash 7.0 stock rom and boot it.
Then re-flash TWRP and it should work fine.
And why you dont write, how you fix it?
Yes, why don't you write instructions for others to have here, and not forcing them to drop a line. What if someone needed these instructions in two-three years time and you simply don't have Moto Z anymore and don't remember how to fix it?
calinorg said:
Yes, why don't you write instructions for others to have here, and not forcing them to drop a line. What if someone needed these instructions in two-three years time and you simply don't have Moto Z anymore and don't remember how to fix it?
Click to expand...
Click to collapse
Yeah, you're right.
I will add it later.
Sorry.
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
The Marionette said:
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
Click to expand...
Click to collapse
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
hypafly said:
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
Click to expand...
Click to collapse
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
The Marionette said:
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
Click to expand...
Click to collapse
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
hypafly said:
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
Click to expand...
Click to collapse
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
So sorry to hear this.
My Moto Z has the WiFi bug too. But Bluetooth works though. It's very annoying because I've tried various fixes and different custom roms which didn't fix the problem. Maybe it's hardware? I wouldn't know. But I'm managing it for now until I get another phone.
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
How to Fix EFS over ADB
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
How to Fix EFS from Bootloader Mode using Fastboot commands
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
How to Fix EFS from TWRP recovery
Boot into TWRP recovery.
From TWRP’s main screen, selectAdvanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.
Edit: Those using twrp may experience efs restoration issues.
While creating the backup of EFS, you will end up with:
efs1.emmc.win (modemst1 partition raw data)
efs2.emmc.win (modemst2 partition raw data)
When restoring this EFS backup, what happened was the file name was not updated for restore, and you ended up with:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs1.emmc.win to modemst2
It should have been:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs2.emmc.win to modemst2
Twrp issue, the steps above will restore your devices.
Click to expand...
Click to collapse
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
eLaDiio said:
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
Click to expand...
Click to collapse
I appreciate the help but it sadly didn't fix anything. :/
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
eLaDiio said:
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
Click to expand...
Click to collapse
I have access to everything, everything besides the wifi, bluetooth and sim functions works.
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
eLaDiio said:
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
Click to expand...
Click to collapse
I't not a hard brick, the phone boots. Wifi, Bluetooth and SIM functions are the only things that are dead. xD
Sorry, I expressed myself badly, what I wanted to say is that your case is a strange situation, by the way, I have a full backup of my phone and if you want, I can share it so you can try flashing it and see if you can recover the wifi, although I think it could end up in a hard brick so it is risky to try it. Tell me if you're interested in flashing my backup
My Realme 6 is kept showing me:
The serial is not match
fastboot_unlock_verify fail
every time I tried to get into fastboot mode Using command adb reboot bootloader,
the bootloader is already unlocked, so I can't enter fastboot mode via the (In-depth Test) App.
It would be my pleasure if anyone got a fix for this problem,
regards
Do u have a solution for this? I was able to unlock but I want to relock and in I'm getting a similar window in fastboot, mine shows this :
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 12, after accidentally updating from rooted android 11 to android 12 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 12.
Any ideas??
leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
soler37 said:
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
Click to expand...
Click to collapse
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Y-YoUsSef-F said:
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Click to expand...
Click to collapse
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
leopseft said:
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
Click to expand...
Click to collapse
Ok bro
leopseft said:
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
Click to expand...
Click to collapse
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Hi, but bro I am in android 12 (F.07) with magisk Root and google wallet (NFC) works great, I think for now not sure if I gonna upgrade to F.09 and losing root access
As my friend @leopseft described our situation, can't enter fastboot mode
soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Actually you can pass the safetynet tests with Magisk modules and magisk hide. But this is another topic. I can help you if you decide to re unlock and root!!
But I have an idea which I wanna try first about the access to fastboot mode.
In the guide you posted there is a step in which you bypass mtk authentication.
(4. Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.))
Did you try to access into fastboot after this step or you continue to the flash process??
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
leopseft said:
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
Click to expand...
Click to collapse
Thank you bro for this solution and I'm so glad you replied to this thread,
but for me, I was able to get into fastboot without this problem after I installed A13 custom Rom (EvolutionX v7.2 UNOFFICIAL)
I used these commands:
adb devices
adb reboot bootloader
As a reminder, my problem was:
The serial is not match
fastboot_unlock_verify fail
Click to expand...
Click to collapse
Thanks again <3
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