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.
Related
I did a very very very stupid thing...
Hey,
Hundreds of times I did this with no problem. But when your head is away bad thing can happen.
I flashed RETUS 5.1 stock ROM over my XT1527 Latin American carrier (possibly Movistar Argentina) . Flash failed. As it turns out I completely forgot to UNLOCK BOOTLOADER first. So I get the code and try to unlock, but the damn ALLOW OEM UNLOCK setting is turned off.
So here I am with a dead phone and no way to boot back. I can only go to (stock) recovery buth nothing I do there really makes any difference. So far I've downloaded two Latin American stock ROM images with no success (Preflash validation failed). However I am concerned that even if I find the right ROM, it will not boot either because of the downgraded boot.
Any options, ideas? Im stuck....Thanks in advance!
Different reason but same problem...
Dang that sucks mate.
Rsd lite to get back to working phone
Sent from my XT1526 using XDA-Developers mobile app
dbx2r said:
I did a very very very stupid thing...
Hey,
Hundreds of times I did this with no problem. But when your head is away bad thing can happen.
I flashed RETUS 5.1 stock ROM over my XT1527 Latin American carrier (possibly Movistar Argentina) . Flash failed. As it turns out I completely forgot to UNLOCK BOOTLOADER first. So I get the code and try to unlock, but the damn ALLOW OEM UNLOCK setting is turned off.
So here I am with a dead phone and no way to boot back. I can only go to (stock) recovery buth nothing I do there really makes any difference. So far I've downloaded two Latin American stock ROM images with no success (Preflash validation failed). However I am concerned that even if I find the right ROM, it will not boot either because of the downgraded boot.
Any options, ideas? Im stuck....Thanks in advance!
Click to expand...
Click to collapse
If you can find someone with a working version of your phone, and in recovery push settings.db (I think) to the bricked phone and reboot into bootloader. then try OEM unlock
Or if you can find an official ROM for the device from Motorola, might be able to flash back to stock with the original firmware then try unlocking again.
sandix said:
If you can find someone with a working version of your phone, and in recovery push settings.db (I think) to the bricked phone and reboot into bootloader. then try OEM unlock
Or if you can find an official ROM for the device from Motorola, might be able to flash back to stock with the original firmware then try unlocking again.
Click to expand...
Click to collapse
I CAN get an identical phone to do whatever I wish with it. However the bricked phone has the stock recovery. Can I still push the file in that?
I have tried with several stock roms with no success. I can't seem to be able to get the correcto one. How do I figure out the correct CID and stuff? However my concern is that the correct stock firmware is XT1527_SURNIA_TEFLA-MSTCL_5.0.2_LXI22.50-53.8_cid12_subsidy-MOVSTLA_CFC and will not boot due to the bootloader being already updated to 5.1
same problem here with xt1528...
Hey XDA, I haven't been on here since my Samsung S2 years ago. I picked up a new moto Z for daydream, (amazon 499 special, 64 gb luna grey unlocked, retus software, 650-03). I bought it from the american amazon, and I am in canada. I popped in my Sasktel sim card and it works perfectly.
My questions are:
How do I manually flash nougat?
If I flash to the rogers 45 firmware, will I still be able to use my Sasktel sim?
How long until nougat comes out regardless? Should I just wait?
If I do flash to this "rogers 45 nougat", can I go back to my "vanilla" stock later? ( i just want daydream now, i bought the headset already. then when my area gets nougat, ill flash back to my phones nougat.. or does it make a difference?)
Sorry for the really random questions. I couldn't find the answers to these on the forums or on google. (reddit has been saying just wait, and don't flash)
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
pixelens said:
...
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
enetec said:
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
Click to expand...
Click to collapse
Going to start a new thread so as not to hijack this one
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own - opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Yes very good tutorial, I really likes to write something like this but I'm not good in English
Thanks again
erfanoabdi said:
...
Thanks again
Click to expand...
Click to collapse
Ahahahaha, this is only "chatting" in not-so-good-English ... :laugh:
Thanx for you *great* development here instead! :highfive:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Wow! Thank you for the response! This answered pretty much all of my questions, but also sparked a few more. The Moto Z was a pretty big purchase for me so I am in no hurry to lose functionality. A lot of people are using translators on here, so I'll be simple (sorry if it comes off as blunt or rude, typing with translators in mind)
I want to stay on android 7. Downgrading to 6.0 is not a worry for me.
I want to get future updates from my carrier. (official android/moto updates and security patches. I want to be able to use the "Google Tango" mod, if it comes out)
I want to be able to use the projector mod and daydream.
I do not plan on rooting my phone (maybe later), and I do not want to unlock my bootloader.
Will the retmx nougat be different then the copy of nougat I would get from retus?
Finally, is there any benefit to waiting for the OTA? Or am I getting the exact same copy of nougat on XDA, that I would in three weeks from OTA? I already bought the daydream headset, am I waiting for nothing?
*two more questions I guess*
Do I need a SD card?
do I need to unlock my bootloader to do this upgrade?
( http://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095)
(http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245)
Sorry for all the questions. I have looked all over XDA and haven't been able to find an answer (reddit, and google too :/). I am hoping that other people will be able to read this, and have their questions answered as well.
Again, thank you. You guys are really smart.
pixelens said:
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Porcelainfog said:
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Click to expand...
Click to collapse
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Based on your expressed needs... I'll just wait your OTA. Nothing more. It's only a matter of weeks anyway...
Sorry for being a newb and asking here but I'm finding it difficult to get my head around this.
I was originally on MM and upgraded to Nougat on unlocked I international Moto Z.
I then decided to install TWRP, root and try a new ROM. If I want to go back to stock Nougat can't it just be a case of flashing the Nougat update I have download on my computer through ODIN or is it going to be a little more complex than that?
Thanks for any help
pixelens said:
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Click to expand...
Click to collapse
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Porcelainfog said:
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Click to expand...
Click to collapse
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
pixelens said:
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
Click to expand...
Click to collapse
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Dawnhawk said:
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Click to expand...
Click to collapse
LOL, of course they did!
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
Porcelainfog said:
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Click to expand...
Click to collapse
Cool. And ya re ADB haha
So I just unpacked my MOTO Z with great anticipation.
However, I immediately ran into the issue where I can't backup my old phone using TiBU and restore it on my new shining gadget. I was VERY unsuccessful rooting the device.
So I went all in and installed RR which I'm using on all other devices as well. Used this TWRP to do it.
While RR is working well, it doesn't have some of the nice things stock ROM had, like the keyboard adjustability, screen on on hand-over and some adjustments in the camera app. Doesn't really matter, but I'd like to give stock another try before I inevitably commit to RR which will no doubt improve in the mean time as well.
Now, for my problem:
Using the recovery mentioned above, I made a full backup of the phone before I messed with it. Now that same recovery doesn't properly restore that backup: the phone doesn't boot when I restore that backup. it never leaves the bootloader unlocked warning screen.
So I figured: bad backup, let's get a stock image. Eh, again no go: motorola doesn't even publish those. So I grabbed the XT1650-03_GRIFFIN_RETEU... from here.
That one again doesn't even fully flash: I tried partial flash (system partition + recovery partition) - which flashed but didn't boot; then tried full flash, starting with the gpt.bin - but this one didn't even flash. reported some errors and that was it.
So, while not bricked, I'm far from any degree of control over my new phone. I'd like to improve that!
Any advice?
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
lollyjay said:
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
Click to expand...
Click to collapse
Yes, "flashing" of the "stock image" I tried to do with fastboot - that series of commands flashing one partition after another with images in the archive. I just didn't want to list all those commands in the post because there's more than 20...
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
doree said:
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
Click to expand...
Click to collapse
Yep, was just about to post how this thread helped. I'm back at stock and seriously contemplating not rooting. I pretty much only need it for one app where I forgot the password and they make it REALLY hard to reset it
i updated to android 12, without any modifications prior, is it possible to root this phone still? or is there no root method for android 12 yet? i've been curious on rooting it for a little while now.
texas7412 said:
i updated to android 12, without any modifications prior, is it possible to root this phone still? or is there no root method for android 12 yet? i've been curious on rooting it for a little while now.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ Reports are saying it works fine.
surgemanx said:
https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ Reports are saying it works fine.
Click to expand...
Click to collapse
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
texas7412 said:
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
Click to expand...
Click to collapse
We have the firehose for the V60!The possibilities are endless..lol..
surgemanx said:
We have the firehose for the V60!The possibilities are endless..lol..
Click to expand...
Click to collapse
i hate to say it.. but the tutorial isn't working for me in qfil it tells me "Please make sure you have selected the correct programmer in flat build page" i rebooted it into the 9008 mode 10-20 times now and it hasn't worked..
texas7412 said:
i hate to say it.. but the tutorial isn't working for me in qfil it tells me "Please make sure you have selected the correct programmer in flat build page" i rebooted it into the 9008 mode 10-20 times now and it hasn't worked..
Click to expand...
Click to collapse
Here,try this one.I just used it not even 10 minutes ago to make a full LUNS back up of a V60 I have laying on my desk.I'm actually using LUNS backups to crossflash other carrier V60's with AT&T software so the VoLTE works.
Edit:Oh,make sure you choose flat build.Then choose this firehose.
surgemanx said:
Here,try this one.I just used it not even 10 minutes ago to make a full LUNS back up of a V60 I have laying on my desk.I'm actually using LUNS backups to crossflash other carrier V60's with AT&T software so the VoLTE works.
Edit:Oh,make sure you choose flat build.Then choose this firehose.
Click to expand...
Click to collapse
this was certainly an interesting experience, i could unlock the bootloader, but doing it via the file thing provided it won't work, going to fastboot and doing fastboot oem unlock, then booting into a twrp recovery and flashing magisk v24.3, it bricked the OS and i had to fight to get it to boot, twrp broke and is locked it refuses to unlock, it gave me an odd looking recovery mode as if it was from android kitkat or something (thats the best i can describe it, it looked much different from the other recovery to wipe) and it said it couldn't boot android and it said to factory reset, so i did.. it downgraded me to android 11 and now its rooted but i can't update to android 12 now because of it being rooted? is there a way to update to 12 now?
texas7412 said:
this was certainly an interesting experience, i could unlock the bootloader, but doing it via the file thing provided it won't work, going to fastboot and doing fastboot oem unlock, then booting into a twrp recovery and flashing magisk v24.3, it bricked the OS and i had to fight to get it to boot, twrp broke and is locked it refuses to unlock, it gave me an odd looking recovery mode as if it was from android kitkat or something (thats the best i can describe it, it looked much different from the other recovery to wipe) and it said it couldn't boot android and it said to factory reset, so i did.. it downgraded me to android 11 and now its rooted but i can't update to android 12 now because of it being rooted? is there a way to update to 12 now?
Click to expand...
Click to collapse
Afraid not because OTA updates will look for rooted or bootloader unlocked devices and will normally give you a white screen error code.Nature of the beast I guess you could say.If you don't plan on doing a custom rom or trying to remove OEM software it's not really worth it honestly.
surgemanx said:
Afraid not because OTA updates will look for rooted or bootloader unlocked devices and will normally give you a white screen error code.Nature of the beast I guess you could say.If you don't plan on doing a custom rom or trying to remove OEM software it's not really worth it honestly.
Click to expand...
Click to collapse
Ahh okay. Thanks though! Do you know why it would have downgraded from 12 to 11 though? that doesn't really make any sense to me.. why did rooting downgrade without me installing an older system or anything like that?
texas7412 said:
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
Click to expand...
Click to collapse
Think about it this way, a V60 with a broken screen is less than 100 bucks. If you brick it, you can fix it for far less than bricking any other phone in a similar class.
texas7412 said:
Ahh okay. Thanks though! Do you know why it would have downgraded from 12 to 11 though? that doesn't really make any sense to me.. why did rooting downgrade without me installing an older system or anything like that?
Click to expand...
Click to collapse
Now,that's an odd one.My thoughts would be because of the engineering bootloader that's written for unlocking purposes?Are you sure it was A12 to begin with?lol..
pflatlyne said:
Think about it this way, a V60 with a broken screen is less than 100 bucks. If you brick it, you can fix it for far less than bricking any other phone in a similar class.
Click to expand...
Click to collapse
And this is very true!The V60 was way ahead of it's time!It's a shame LG devices were never marketed properly and supported on a local retail level like they should have been.And even if you did brick them,worst thing would be peeling the back off and hitting the testpoint to bring it back to life.
surgemanx said:
Now,that's an odd one.My thoughts would be because of the engineering bootloader that's written for unlocking purposes?Are you sure it was A12 to begin with?lol..
Click to expand...
Click to collapse
Yes! I was so excited that i got 12 on it, the bootloader shows its android 12 though.. which is really confusing to me.. is there any chance there's an android 12 kdz for this phone floating around that i could try to root and flash? i'm kind of regretting it now, i can't get the fingerprint scanner working following the tutorial there.. i can't update to 12 again it just fails to download, my recovery mode is gone, i can't get back into the bootloader/fastboot mode only EDL mode but it won't recognize anything within windows, adb won't work nor fastboot, can i recover it still if i wish to go back to stock?
The good news is, it gets much better benchmark scores and is much much faster..
on geekbench, 1688 single core, 6203 multicore, it had a higher score but said it was invalid? that one was 4067 single core, 15601 multicore
antutu, it scored 695755 with just using kernel auditor and maxing out the cpu freq and setting gpu freq to 870mhz.
Edit: I just remembered, for where you mentioned the bootloader, i don't have the engineering one installed. i never got that far to even install it. just android debugging > oem unlock > fastboot > fastboot oem unlock
texas7412 said:
Yes! I was so excited that i got 12 on it, the bootloader shows its android 12 though.. which is really confusing to me.. is there any chance there's an android 12 kdz for this phone floating around that i could try to root and flash? i'm kind of regretting it now, i can't get the fingerprint scanner working following the tutorial there.. i can't update to 12 again it just fails to download, my recovery mode is gone, i can't get back into the bootloader/fastboot mode only EDL mode but it won't recognize anything within windows, adb won't work nor fastboot, can i recover it still if i wish to go back to stock?
The good news is, it gets much better benchmark scores and is much much faster..
on geekbench, 1688 single core, 6203 multicore, it had a higher score but said it was invalid? that one was 4067 single core, 15601 multicore
antutu, it scored 695755 with just using kernel auditor and maxing out the cpu freq and setting gpu freq to 870mhz.
Edit: I just remembered, for where you mentioned the bootloader, i don't have the engineering one installed. i never got that far to even install it. just android debugging > oem unlock > fastboot > fastboot oem unlock
Click to expand...
Click to collapse
That depends on what model of V60 you have?Most of the kdz files for Verizon or T-Mobile can be found at the link below.AT&T or Sprint no kdz's to be found except back up Qfil copies I have found.Take a look,and LGUP it if you find the firmware you want.Most will be A11 and you can just OTA back to A12 with no problem.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
surgemanx said:
That depends on what model of V60 you have?Most of the kdz files for Verizon or T-Mobile can be found at the link below.AT&T or Sprint no kdz's to be found except back up Qfil copies I have found.Take a look,and LGUP it if you find the firmware you want.Most will be A11 and you can just OTA back to A12 with no problem.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
Click to expand...
Click to collapse
okay good! Thank you! Is there any chance of a android 12 KDZ for the t-mobile variant? and if i flash back an original KDZ, will i have to wipe everything again? Thanks.
texas7412 said:
okay good! Thank you! Is there any chance of a android 12 KDZ for the t-mobile variant? and if i flash back an original KDZ, will i have to wipe everything again? Thanks.
Click to expand...
Click to collapse
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
surgemanx said:
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
Click to expand...
Click to collapse
do i have to refurb to go back to stock, or can i do it via the upgrade option? Sorry if i'm being bothersome lol
surgemanx said:
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
Click to expand...
Click to collapse
HEY! SO I FLASHED THE STOCK BOOT A AND BOOT B AND THEN IT LET ME UPDATE TO 12!
i let the update do its thing, reflashed TWRP and then flashed the patched boot a and b, now i have a rooted android 12. WOOHOO!
texas7412 said:
HEY! SO I FLASHED THE STOCK BOOT A AND BOOT B AND THEN IT LET ME UPDATE TO 12!
i let the update do its thing, reflashed TWRP and then flashed the patched boot a and b, now i have a rooted android 12. WOOHOO!
Click to expand...
Click to collapse
Yes,that wil work until the next update.If it's modified when the next OTA hits,it will give you the update error.Basically,you just set it back stock and the update works.But,glad you have it worked out.
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