How to manually get nougat? - Moto Z Questions & Answers

How to manually get nougat? - Moto Z Questions & Answers

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:

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

Related

[GUIDE] How to sideload the Nougat soak test onto your G4. [TEXT TUTORIAL]

AMAZON VARIANT NOW SUPPORTED!
NO PC REQUIRED AT ALL FOR THIS TUTORIAL!
READ ME: I am not responsible for bricked/damaged devices from following this procedure. It should be safe, if done right on the supported models. This does not void your warranty, but it is soak test firmware, meaning that it is beta software, and might have bugs/issues. I haven't noticed any myself, however.
Alright, I am aware that there are already videos describing how to install Nougat, but this is a (fairly) easy to follow text tutorial.
Step 1: Make sure your running the latest Marshmallow.
Before you can install the Nougat update, you have to make sure that you are running the latest Marshmallow firmware for your device. If your phone is running the MPJ24.139-63 firmware, you are good to go. Anything lower, and you will have to update your firmware, either manually, or through the OTA checker.
HAVE A NEWER FIRMWARE? (OR AMAZON VARIANT)
I had a link to a Reddit user's guide to do this, but they have apparently deleted their account, so I'll link this guide from XDA: http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
UPDATE: Download this file and flash it in recovery the same way that you install Nougat, to update to the latest Marshmallow firmware, if you are on anything lower than MPJ24.139-63: https://docs.google.com/uc?export=download&confirm=mkUs&id=0BzpjDRtfDv8PdER0cml3VzRHZTA
Step 2: Download the Nougat OTA File.
Follow this link to download the Nougat OTA file: http://downloadmirror.co/Uq5/Blur_Version.24.31.64.athene.retail.en.US.zip
Step 3: Boot into Recovery.
You have to boot into recovery to sideload this OTA file. First, power off the device completely. When it is completely powered down, hold the Volume Down button, and then the power button, not letting go of either button, until an Android appears, with a bunch of text. You are now in Fastboot Mode. Press the Volume Down button until you see Recovery Mode, then hit the power button.
Step 4: Install.
Once you are in Recovery, you may see an Android logo again, with the text "No Command" below it. What you need to do here is hold the power button, and whilst holding the power button, press Volume Up, to access the menu. It is easy from here. You need to select the option to install update from SD Card, using the Volume buttons for navigation, and Power to select. From there, you find where you downloaded the BLUR_VERSION.24.31.64.ATHENE.RETAIL.EN.US.ZIP file, and select it. It will start installing the official Nougat OTA. Give it some time, upwards of 15 minutes to install. Once it has complete, simply select the Reboot system now option, and if all went well, you should see the "Android is upgrading" screen, and now you are running official Nougat soak test on your G4.
NOTES - The install may hang on the "Patching system image after verification." message. Give it around 5-10 minutes, it will eventually pass that stage.
I can't guarantee that this method will work on all G4 variants. I can confirm it works on a UK Retail XT1622, however.
This may make it harder to install the stable official Nougat when that releases worldwide, I am not sure yet if it affects the upgrade path to the stable firmware.
KNOWN ISSUES
I actually have not found any issues with this firmware yet, it appears VERY stable for a soak test build. If you have come across any, or need help, comment below.
COMPATIBLE MODELS
These models have said to have had success with this update.
XT1643 - Moto G4 Plus Dual-SIM (India)
XT1640 - Moto G4 Plus Dual-SIM (Brazil)
XT1642 - Moto G4 Plus
XT1622 - Moto G4
XT1626 - Moto G4 (India)
DOWNGRADE TO MM FOR OFFICIAL NOUGAT OTA WITHOUT BOOTLOADER UNLOCK
Follow this guide from the Moto G4 Plus XDA section to downgrade your G4 to Marshmallow to install the official Nougat OTA:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296

Welp, can't apply the MPJ24.139-63 update on XT1621 lol

Does it work on the xt1625 non amazon, MPJ24.139-64 ?

traceable ? (sorry not good at this title thing)
Hey thanks for sharing this.
I just wanted to ask whether or not Motorola/their repair service will be able to tell if I applied this update (meaning if I roll back to older firmwear without unlocked bootloader), since I sent my Moto G4 in for a repair but apparently since it came back yesterday the issues came back.
So I just want to make sure whether I can try this without them blaming it on me "flashing unfinished software" once I'll send it back for a repair/replacement
Thanks in advance

Yoloswaggerboy69 said:
Hey thanks for sharing this.
I just wanted to ask whether or not Motorola/their repair service will be able to tell if I applied this update (meaning if I roll back to older firmwear without unlocked bootloader), since I sent my Moto G4 in for a repair but apparently since it came back yesterday the issues came back.
So I just want to make sure whether I can try this without them blaming it on me "flashing unfinished software" once I'll send it back for a repair/replacement
Thanks in advance
Click to expand...
Click to collapse
They dont seem to care, they just reflash and send it back.

Rempala said:
They dont seem to care, they just reflash and send it back.
Click to expand...
Click to collapse
Thanks a bunch

Cyberneticx said:
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
Click to expand...
Click to collapse
It does not. It checks your current firmware version and that one is too NEW. I have the same. I got this: http://i.imgur.com/ggmBiMZ.jpg

Cyberneticx said:
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
Click to expand...
Click to collapse
mattgoldey said:
It does not. It checks your current firmware version and that one is too NEW. I have the same. I got this: http://i.imgur.com/ggmBiMZ.jpg
Click to expand...
Click to collapse
I have added a way to downgrade your firmware to install the update.

LoopingCreeper said:
I have added a way to downgrade your firmware to install the update.
Click to expand...
Click to collapse
Do I have to root the phone to downgrade?
I went to the link and I think it was a different version.
I bought mine on the motorola store and it's a custom phone. It came as xt1625 but there is no amazon nor anyother thing on it

Cyberneticx said:
Do I have to root the phone to downgrade?
I went to the link and I think it was a different version.
I bought mine on the motorola store and it's a custom phone. It came as xt1625 but there is no amazon nor anyother thing on it
Click to expand...
Click to collapse
You don't have to root or unlock your bootloader or anything like that. I believe that G4 and G4+ ROMs are interchangeable.

LoopingCreeper said:
I have added a way to downgrade your firmware to install the update.
Click to expand...
Click to collapse
That reddit post is deleted and the person that posted it deleted their account. Not sure I'd be comfortable downgrading now.

Can anyone confirm XT1621? Would it be safe to bet that it'll work if XT1622 is working?

Thank You, i have MOTO G4 with Nougat,
no need to downgrade the bootloder because i was on MPJ24.139-63, this worked with XT1622 - Moto G4 bought from Romania.
"Patching system image after verification" was like 15 minutes and when i choose reboot the led in the bottom of phone was flashing,(strange, i was reading about this led on xda) i hope will function in Nougat .

this does not work in any way shape or form with the XT1625 retail or amazon variants.

If I were upgrading from stock marshmallow to stock nougat and not performing a factory reset I would completely understand why i need to be on the latest version. However, I'm coming from a cm based ROM and will have to do a factory reset anyways. The firmware file includes the most up to date bootloader, soooo why do I need to flash -63 before flashing -64? Is there something I'm missing here or am I correct?
(I'm on Retus XT1625, non Amazon prime variant with an unlocked bootloader)

Travisholt92 said:
If I were upgrading from stock marshmallow to stock nougat and not performing a factory reset I would completely understand why i need to be on the latest version. However, I'm coming from a cm based ROM and will have to do a factory reset anyways. The firmware file includes the most up to date bootloader, soooo why do I need to flash -63 before flashing -64? Is there something I'm missing here or am I correct?
(I'm on Retus XT1625, non Amazon prime variant with an unlocked bootloader)
Click to expand...
Click to collapse
short answer to your question: the nougat ROM looks for a -63 boot image, and also verifies against baseband versions.
it doesn't matter though, because the Nougat ROM linked herein will not work on a XT1625. i have spent hours trying to make it happen.

trevorcobb said:
it doesn't matter though, because the Nougat ROM linked herein will not work on a XT1625. i have spent hours trying to make it happen.
Click to expand...
Click to collapse
What error are you getting when you try and flash it? I tried, but my firmware version was newer than the expected version, so it refused to flash.

I tried this on a locked bootloader with XT1625 amazon prime phone.
I am getting the error This package expects the value "athene" for "ro.product.name" or "athene" for "ro.product.name" on the OEM partition; But the actual value are "athene_amz""athene_amz"

It'll probably work on the non-Amazon version, then.

I have Adoptable Storage and the ZIPs don't show up in the SD card. Is it safe to swap to another card temporary to do the update?

HUAWEI HR5 [KII-L05] (Canadian Rogers)

I have this canadian version of Huawei honor 5x, and I've been scouring to find answers to whether if am i able to flash a custom rom such as cyanogenmod or not. Can anyone please help me out with this; I've already made several post and it get unanswered. Sofar I've managed to unlock the bootloader, flashed twrp, and rooted it. When I tried installing CM 13 from a thread on this site, I always get the "error 7" and I tried deleting the 2nd line in the meta-inf and rezipping the rom and reflashing; results remain the same.
Here's more info on my phone:
Build#: KII-L05C654B330
EMUI 4.0

Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.

Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Hai bud , he mentioned that he is on emui 4 . So we have necessary proof that he is on marshmallow which we require to flash a rom on 5x:highfive:

And after thinking for a while , the last version (latest updates) have modem issues so custom roms may have stopped working for u due to this. I have solutions for u .

Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse

Goldenmeadow said:
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Click to expand...
Click to collapse
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.

Thanks for reply! With the help of fellow members I figured it out - I was holding POWER button TOO LONG And if that happens, phone goes into built in recovery... You suppose to let button go once you see first splash screen.
So it's all good!
Thanks!!!
Chaos Storm said:
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Click to expand...
Click to collapse

Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs

kenneth_82614 said:
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
Click to expand...
Click to collapse
I will have a look. As things would be, I also need to restore my GR5 so I'll find it for both of us.

CM13 or LOS13 on Nougat bootloader possible?

Hey there,
I acquired recently (actually today) a Moto Z (XT1650-03 reteu) and was spending the whole day to get stock marshmallow/mmbl (marshmallow bootloader) on it.
After several hours of trial and error I gave up.
Now I hope someone with experience in LineageOS (and in compiling it) could answer my question (before I spend more hours on trial and error).
Is it possible to compile LineageOS 13 for the Nougat bootloader?
I don't mind to compile it myself with my little knowledge but I need to know if it is possible at all.
I need Marshmallow for XPosed, I cannot live without it. Before I give up XPosed entirely, I need to try any way to get Marshmallow working.
The alternative might be to buy a Moto Z Play (which seems to be able to downgrade).
I hope one of you mighty users can answer my question with a direct answer or with a "yes with modifications not done by a noob".
(In things of compiling I am a noob but I think I am able to read some experience up for trying.)
Many thanks for any constructive comment on that!

I have been working with moto phones since the Moto G 4G (peregrine).
You could compile cm13 (as the Z has 6.0 blobs) but I would not recommend it for these reasons:
You would need to make a vendor tree for Android 6.0.
You would need to back-port the current device tree(7.0/.1). I don't believe we got anything working on cm13 back in the original bringup. The Verizon Z came out with 6.0.
You would need to set up a completely new selinux policy (not worth the hassle alone).
You would need to grab the kernel source from Motorola and add in the patches needed to get it building on aosp.
You will most likely have a flickering display/brightness bug when flashing older firmware on a newer bootloader.
You cannot go back to an older bootloader once upgraded. Attempting to do this will possibly brick your bootloader partition.
It's honestly not worth the hassle. We're talking about serious man hours bringing it up for 6.0. You could always wait for Xposed to come out on N. You could always flash the stock system, boot partitions and you may be able to get back to M. iirc the radio (ril/modem) will most likely function poorly (or not at all).
Don't get me wrong, the Z play is an awesome phone and you shouldn't consider it a downgrade! I sometimes wish I would have gave my dad the Z and picked up the Z play. One drawback to the z play is the lack of arm64 support due to the processor.
Hopefully I've answered your questions.
Sent from my XT1650-03 using Tapatalk

Thank you, that is mostly what I thought, but much more complicated than I hoped.
I won't be able to do that.
My bootloader is already on Nougat (it was shipped with it). I tried downgrading the bootloader but fastboot doesn't let me do that. (Security downgrade is obviously not allowed.)
Actually I was playing with the thought to only downgrade aboot and then (if it worked) downgrade the rest, if it doesn't work I can flash a nougat aboot backup back with a CFW or TWRP (booting to it over adb reboot recovery).
But all this without flashing gpt.bin (the riskiest part) and because of this my plan might not work.
The aboot of MM would have to be backed up and uploaded from some XT1650-03 user. Actually I would need everything in bootloader.img to test it a little more... just in case. But I don't know if I should go this way.
I know RSDLite, I tested (today) a program called "qboot" (which didn't work correctly), so I might be able to recover a brick... but there's still a risk.
I actually don't see the Z Play as a downgrade but it is thicker. The Moto Mod for which I am waiting for will be pretty thick and I try to avoid any unneeded thickness. (Keyboard mod)
Actually I don't believe that XPosed for N will be released within the next few months or... even worse, not this year.
I will try to find replacements for the almost 20 modules I use with XPosed. If I am not satisfied, I will try a downgrade.

I'd be careful with playing around with aboot. If you flash a corrupt or incompatible image then your device is going to be permanently bricked. You will not be able to get back into recovery nor have fastboot powers. I'd strongly recommend forgetting about going back to M at this point and looking for alternatives.
Motorola has built in checks that may not allow it to boot after it's flashed.
Sent from my XT1650-03 using Tapatalk

I guess you're right.
Without the ability to boot straight into recovery and without a 100% method of unbricking, it is too risky...
Just a thought:
With the ZTE Axon7 (nearly the same system) you can boot straight into recovery. You need to flash aboot with the ability to unlock the bootloader, at least on the global version. If flashing fails, you can boot into the recovery (signed twrp) and flash your backup.
But the Moto Z has no way to boot straight into recovery, so it is even more risky.

Root honor 7x without disable ota without twrp

Hello guys this guide is for who want to root phone without disabling ota updates.
(BOOTLOODER SHOULD BE UNLOCK)
BIG THANKS FOR MAKING PATCHED BOOT IMg @Jan.Pul
IAM NOT RESPONSIBLE FOR ANY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
1)Download patched boot.img from link below
2)copy that patched boot.img to your adb folder
3) adb debugging should be on and oem unlock should be on for unlock bootlooder
4)turn off your device and go into fastboot mode by pressing holding volume down and power key
5) check whether fastboot detect your device or not by typing this command on (cmd) FASTBOOT DEVICES
6) if fastboot shows that your device is connected your good to go
7) you need to boot into patched boot.img for this type a command FASTBOOT BOOT patched_boot.img your device will boot automatically
8) download magisk manager apk from google and. Open ur magisk manager and install ad direct method and reboot
If you get bootloop dont worry just press your power key for 5sec it will boot automatically
PATCH BOOT IMG : https://drive.google.com/file/d/1cU6qOMiHlGdSAbRtMVgTlHummcGksnt6/view?usp=drivesdk

Guessing this is for the Indian/Chinese version and the bnd-l24 is still sitting on the shelf? And rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?

Yes..But Why?
maximran said:
maximran said:
this guide is for who want to root phone without disabling ota updates.
(IAM NOT RESPONSIBLE FOR AMY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
Click to expand...
Click to collapse
str8stryk3r said:
rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Click to expand...
Click to collapse
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse

RaiderWill said:
maximran said:
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse

A Question Sir..
str8stryk3r said:
RaiderWill said:
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse

RaiderWill said:
str8stryk3r said:
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse

@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?

str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse

kilroystyx said:
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
Click to expand...
Click to collapse
It will not work

Interesting!
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
Asder.mko said:
str8stryk3r said:
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Well, I got the OTA in December itself but since I had rooted and installed twrp recovery, I wasn't able to install the update.
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
Click to expand...
Click to collapse

RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Before I went ahead an unlocked my bootloader I checked as many sources as I could about if whether or not I'd still be able ota update and the vast majority of the things I read states that what causes the update to fail is not having stock rom and not having stock recovery. The bootloader being unlocked doesn't modify those or any system files so everything should be fine. Unless Huawei changed things specifically for our Honor 7x then there shouldn't be any problems with ota updates. I guess I'll find out when the L24 people start saying they got updates and I don't receive it or can't install it
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Well, that's quite right. I don't know whether Huawei/Honor implemented THAT thing, but yeah reverting back to stock conditions wand applying OTA wouldn't be an issue!
( P.S - I'm stuck here too as I have OTA update since December but haven't reverted to stock to install it. I don't yet know properly about manual installation! )

(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)

iammudd said:
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
Click to expand...
Click to collapse
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.

str8stryk3r said:
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
Click to expand...
Click to collapse
No need for full fw broh need vendor partitions, device tree, kernel sources

maximran said:
No need for full fw broh need vendor partitions, device tree, kernel sources
Click to expand...
Click to collapse
Lmao, and that's why I'm not a developer. I just know having the stock image files is important so that when something gets screwed up got have something to fall back on.

Bringing Up The Rear...
Asder.mko said:
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.

RaiderWill said:
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
Click to expand...
Click to collapse
People like to root and mod their own devices for their own reasons but you're right, a lot of the reasons I modded past devices was because the roms almost always ran better than stock but the 7x imho runs great. Used to be kernels for better battery life and such. I like custom roms because I like to be able to do certain things that stock roms limited as far as customizing goes. A lot of people hate bloat and end up deleting every file on the phone that isn't necessary or to their liking to make the rom as minimal as possible.
But as of now I'm happy with the phone and don't feel the urge to need to root and and a custom recovery. The roms that eventually come would have to offer something worthwhile to flash. But hell, that's subject to change given how I'm feeling that day lol. There's a new AOSP based rom in another thread that sounds promising

RaiderWill said:
Will Huawei / Honor release a stock image of Nougat and Oreo ? ...
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x..
Click to expand...
Click to collapse
I assume that you already know this ... but I should mention it for others that you can run TWRP (if there is a version for one's phone) without flashing it. (I don't have my 7x yet, so I prob really shouldn't be trying to give detailed instructions anyways.) From there, you can make backups of the stock image, stock recovery, etc. (So thx again to this forum for reminding me that I should backup all stock images as soon as I receive my 7x so that MY fingerprints are not all over the backups.)
As to rooting, there ARE at least 2 things that Huawei hasn't provided without root:
Yes, I can make app backups (and/or use the Huawei "easy transfer"... not sure what app that is at the moment) but I'd assume that I won't be able to transfer it to a non-Huawei device. That's why I continue to use Titanium Backup.
USB Mass Storage Enabling (and by extension Selinux Passive mode). I want fast transfer to my desktop, etc.... and I want a drive-letter (yes, there are Win programs which only work with drive letters). Without UMS, I haven't found a way to do that.

Question Best usable ROM ?

Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn

Tried them all. Evolution X is the most often updated and works the best for me.

Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...

Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.

wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.

Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.

wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/

wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!

Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks

vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!

Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?

So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks

Better Mobile App

welcome