Related
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
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.
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
jamesvmccann said:
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
Click to expand...
Click to collapse
There are stock ROMs (H83020a and H83020c) available to flash from twrp. You will not lock your bootloader nor lose twrp; but in order to get root again(in case you want), you will need to flash su. It worked for me perfectly and I have no issues with anything on my phone. The only thing that does not work (check screenshot for details) is google pay because since the phone is rooted "it does not meet the google's security standards." Now if you want to return the phone to factory state I believe there are threads here for that. If you still want to keep the phone just flash the appropriate zip and enjoy removing tmobile bloatware if you wish.
LG G5 Downloads:
Important!!!Do not flash H83010a. I read that it can brick your phone.
TMobile model is H830.
Android 6.0.1 is H83010i
Android 7.0 is H83020a and the latest version is H83020c. Find the zip of your choice.
http://downloads.codefi.re/autoprime/LG/LG_G5
jamesvmccann said:
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
Click to expand...
Click to collapse
Ok. If you're wanting to do 100% stock, download the complete zip for 20c from http://downloads.codefi.re/autoprime/LG/LG_G5/H830/H83020c/LG-H83020c-Flashable.COMPLETE-ARB01.zip there. Put it on your extsd card. Backup everything that is on your internal sd (phone memory) like pictures, videos, SMS, etc. Once you've done that, boot to TWRP. Once in TWRP wipe everything except externalsd card, I also recommend using the format option to format the internal sd. Once you've wiped and preferably formatted data go to install and install the 20c complete zip you put on your extsd card. After it's done installing just reboot. This will overwrite TWRP and you will NOT have root. Your bootloader will still be unlocked though, so you still need a PC to relock your bootloader. Also I don't think encryption will be re enabled unless you flash the kdz though. Anyways that's your best way to return to stock without using PC.
mlatelcom said:
There are stock ROMs (H83020a and H83020c) available to flash from twrp. You will not lock your bootloader nor lose twrp; but in order to get root again(in case you want), you will need to flash su. It worked for me perfectly and I have no issues with anything on my phone. The only thing that does not work (check screenshot for details) is google pay because since the phone is rooted "it does not meet the google's security standards." Now if you want to return the phone to factory state I believe there are threads here for that. If you still want to keep the phone just flash the appropriate zip and enjoy removing tmobile bloatware if you wish.
LG G5 Downloads:
Important!!!Do not flash H83010a. I read that it can brick your phone.
TMobile model is H830.
Android 6.0.1 is H83010i
Android 7.0 is H83020a and the latest version is H83020c. Find the zip of your choice.
http://downloads.codefi.re/autoprime/LG/LG_G5
Click to expand...
Click to collapse
Just curious what type of brick? Hard or soft? Just wanna know for future safety
Sent from my LGE LG-H830 using XDA Labs
Nick216ohio said:
Just curious what type of brick? Hard or soft? Just wanna know for future safety
Click to expand...
Click to collapse
I don't remember very well; but I believe it's hard brick. When I was researching to root my phone y read that somewhere, maybe here. I'll try to find the info on my PC when I get home.
Update:
I found the link. The advice is in the FAQ. Not sure if that would happen in your case since you have a custom ROM. The danger is when downgrading from H83010D to H83010A.
Here is the link:
https://forum.xda-developers.com/tm...ock-h830-10d-rom-flashable-zips-imgs-t3406505
mlatelcom said:
I don't remember very well; but I believe it's hard brick. When I was researching to root my phone y read that somewhere, maybe here. I'll try to find the info on my PC when I get home.
Update:
I found the link. The advice is in the FAQ. Not sure if that would happen in your case since you have a custom ROM. The danger is when downgrading from H83010D to H83010A.
Here is the link:
https://forum.xda-developers.com/tm...ock-h830-10d-rom-flashable-zips-imgs-t3406505
Click to expand...
Click to collapse
Thanks bro. I totally believe it because past phones had exact issue.
Sent from my LGE LG-H830 using XDA Labs
Just for clarification, if you're on Android 7, you can not downgrade to Android 6 without first downgrading your bootloader as it won't flash correctly. Also just something to always keep in mind with LG phone's at least, is that LG uses a antirollback system. Never attempt to downgrade from a higher ARB # to a lower ARB #, if you're somehow successful it will lead to a hard brick. Every firmware that autoprime has posted states what antirollback number it is on, so always check that. On h830, every firmware since 10D has been ARB01, only 10A or earlier was ARB0. While lgup shouldn't allow you to flash (should error out), no reason to take that chance. Hopefully that helps clarify
Note: You can try this with EU ROMs but I'm not sure if it will work, and won't be testing to see if it works, since I see no reason to flash EU ROMs anyways.
I knew this from day 1, but was switching between various LOS ROMs so didn't have much inspiration to make a guide. Now i'm switching back to Stock-based ROMs (due to other roms having no dolby, no voice capture,...), I'll be making a guide
I'm not responsible for bricked device.
This is a guide for those who are facing issues when trying to flash US, EU stock and stock-based ROMs on the chinese axon 7 (no signal, no wifi, worse battery, or simply not booting after splash screen). Since downgrading is also a part of this guide, I will also be covering how to downgrade Nougat 7.1.1 ROMs back to 6.0.1 Marshmallow.
Important thing to note:
You must be on B13, 6.0.1 marshmallow with stock recovery, and please, DO NOT UPDATE TO B10 China NOUGAT or anything above ! This will cause a lot of problem, as from what I've deduced, US B19 is based on the China B09 update, anything above B10 won't be backwards compatible. and will cause problems like not booting, (or no wifi, signal etc after you recover the boot partition through recovery)
Now, if you're already on Nougat and want to try this guide, downgrade back to Marshmallow using EDL. Try this guide:
- Download B13 EDL (credits to djkuz from 4pda), extract it
- Download and install the latest Xiaomi MiFlash (stable or beta)
- Turn off your phone, plug it in to your PC, Hold Power + Vol Up + Vol Down, go to device manager, look for the "Port" section, and you will see something like Qualcomm HS-USB QDLoader 9008., if you see it, proceed down below. If not try again.
- right click , open properties on the Qualcomm HS-USB QDLoader 9008, go to port settings, if you see the speed is at 9600 bits per second (bps), change it to 128000 (you can skip this step, but doing it will increase your flashing speed)
- Open MiFlash, press select and pick the folder you extracted a few steps ago.
- Press refresh, if you see your device appearing on the list, press flash. (if some random errors appear, unplug the device, plug it back and immediately press refresh and press flash)
- After flashing you'll be back on B13 China Marshmallow.
REMEMBER, DON'T OTA UPDATE IF YOU WANT A SMOOTH TRANSITION TO US ROMS:
Now, to the good part:
- Download the B09 China OTA package from here (credits to Demons-77)
- put the package into your EXTERNAL sd card, internal won't do.
- reboot to recovery (Power + Vol Up)
- select the option with the word "sd" on it
- now go and pick the package that you just put in
- It will begin flashing and after that, you will have B09 China Nougat
- reboot to bootloader and install recovery (fastboot flash recovery *your file name*)
- after that you can install any roms you like, no need to backup and restore the boot partition every time you flash a US ROM, and you won't encounter strange issues like no boot, no wifi, etc.
TL;DR for those who already know how to do most of these: go back to China Marshmallow through EDL, update to B09 China Nougat with stock recovery, install TWRP and then flash whatever US stock or stock-based roms you want (just like how you would with a US phone)
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
otaconremo said:
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
Click to expand...
Click to collapse
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
spiwar said:
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
Click to expand...
Click to collapse
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Fuilares said:
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
Click to expand...
Click to collapse
Downgrading IS a part of this operation if you're already on Nougat (you need to go back to MM before you can go B09 Nougat). Why relock your BL though? Magisk root can work with Android Pay, Pokemon Go AFAIK, not sure though (since I don't use any of those apps)
tigrey said:
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Click to expand...
Click to collapse
Yes that stock ROM will be okay. Personally I'm using the latest version of BadBoyz ROM.
No you can't. Because OTA updates requires the stock recovery, and your phone probably won't boot if you flash the US Stock recovery
otaconremo said:
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Click to expand...
Click to collapse
Magisk won't work if you're using B10 Chinese as a base (as mentioned above), if you flash on B10 you'll have to flash the boot portion from the stock Chinese ROM for the US ROMs to even boot, and then you just lose magisk.
I see. Thanks for the tips. But I don't think I'll be coming back to b13 mm for that. I hate restoring data ang all the files in my internal storage.
Hi!
Could you please clarify me a doubt?
To follow this guide, must my device already be rooted?
Thanks!
Well, first part went well. After a lot of effort, because device was recognised as DFU. Anyway, I got it back to B13 with stock recovery.
On second part, when I try installing the FOTA update, it fails, giving me error: status 8. In update history, it says that the system package did not match the phone. Obviously I have A2017.
Any suggestions?
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
I am just getting back to messing around with phones after about 5 years. So many things have changed and I am trying to get answers here as well.
I used TWRP and Magisk to root my phone. Installing TWRP will not wipe your data as it is flashed to a different partition but to install TWRP you have to unlock the bootloader and that will wipe your userdata. And no, I don't believe there is any possibility of rooting without unlocking the bootloader. If you decide you want to go back to stock, there are stock roms available and you can re-lock the bootloader on the N10 so you should be able to set it back to just like it was when you first bought it. I say should because I have never done it, just read that it can be done when I unlocked and flashed mine.
I wish I could be of more help but so many things have changed in the years since I've been away from doing this stuff I feel like a total noob again.
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
No I do not believe there's a way to gain root without flashing anything. There's no need to backup anything you can always use the MSM download tool to restore your device. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ You should be able to find most of the stock imgs on here already if you'd really need to flash back. I'm no expert either, just my experience with this phone in particular has been pretty straightforward. I never backed up anything lol.
Twrp is iffy i made a backup I'll never use, check out the post about flashing international rom to tmo and metro devices, that's my backup. Also you can run 11.0.3/2 firmware and boot 11 gsi's the post about lir rom has the info. Flash the product_gsi.img referenced there, I have never deleted my product partition and I only leave oos ten installed long enough to take ota's. There are more roms in the source forge page referenced with lir rom post. Flash magisk via recovery, either side load or twrp, pay attention that it flashes partition sda14(super image) or wifi breaks.