Develop Bugs

RETUS Nougat Firmware Package?

I've been searching high and low for a full nougat firmware package for the RETUS model... and i cant find one. Has anyone else found one?
I know there are OTAs out there, I'm looking for an FXZ that can be used with fastboot.
filefactory, mirrors.lolinet, etc... seem to have most 7.0 firmware packages EXCEPT for RETUS which only have 6.0 packages.

I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.

Jimi Mack said:
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Click to expand...
Click to collapse
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.

FanDroid09 said:
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
Click to expand...
Click to collapse
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?

chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
What did you do to root? Unlock bootloader then what?

chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.

EspElement said:
What did you do to root? Unlock bootloader then what?
Click to expand...
Click to collapse
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
FanDroid09 said:
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
Click to expand...
Click to collapse
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.

Does anyone know where to get the latest either RETAIL or RETUS stock firmware with the May 1st security update? NPN25.137-24.4

chris23445 said:
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Click to expand...
Click to collapse
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader

EspElement said:
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
Click to expand...
Click to collapse
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.

chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
Is it worth after all?

chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
I've been there done that that's for sure. I just bricked one of my Moto Z plays last week doing what you were about to do.

StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.

tpx00 said:
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
Click to expand...
Click to collapse
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh

EspElement said:
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
Click to expand...
Click to collapse
Ya I'm about to go pick up a nexus 6 from craigslist until mine comes back from Motorola.

Problem with RETEU firmwares on chinese ADDISON_RETCN (XT1635-03)

I have tried to update my chinese XT1635-03 to 7.1.1 with OTA through ADB sideload and unfortunately it is not working.
I have sucessfully flashed the phone with reteu latest firmware with April security patch (ADDISON_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) through fastboot.
But once I try to sideload 7.1.1 OTA (Blur_Version.26.1.22.addison.retail.en.US) the process terminates at 47% with notification that the package expects product name "addison" but actual value is "addison_retcn"
Is it possible to either change the product name or disable such check of product name? It seems to me, that at the moment there is no way to flash OTA and I need to wait for full 7.1.1 image.

Reading similar questions around, I have to ask. Why you people cannot wait couple of weeks to get OTA? Instead of risking to brick your device?
New update is not bringing revolutionary/awesome/amazing/mind blowing... new features. I understand if it's update to completely new Android version or that your device/region will not get update at all.
Sent from my XT1635-02 using Tapatalk

You have XT1635-03 and the update is for XT1635-02. So if you have a reteu phone you can really update over sideload without issues. And yes, I need android 7.1.1 and I wouldn't wait one day longer. I need app-shortcuts, because I had this on my old phone, too. There was android 7.1 since the first day. But if you don't have it before you can't miss it. So you can wait much easier For me it was important for other issues, too. For example Wifi problems and stability fixes and over 100 security fixes. Many reasons for the update
Edit: And one more reason for the update: To help google to get more than 0.6% for android 7.1 We should update all, otherwise android 7.1 will never get 1%
Everybody should help to get this 1% maybe next month. So update, just do it for the 1%, yes xD
:silly::good:

The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.

freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
The point is, how can you change the channel...

freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
OK, makes sense for you but for many/most others is just matter of time.
I'm not blaming anyone. Do whatever you want with your phone, just be ready if something goes wrong

The surprise was a different phone name. Different channel is usually not a problem

freeman_g said:
The surprise was a different phone name. Different channel is usually not a problem
Click to expand...
Click to collapse
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED

flashallthetime said:
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
Click to expand...
Click to collapse
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?

allrightlite said:
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
Click to expand...
Click to collapse
I have no idea

flashallthetime said:
I have no idea
Click to expand...
Click to collapse
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.

allrightlite said:
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
Click to expand...
Click to collapse
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.

dandrumheller said:
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
Click to expand...
Click to collapse
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.

allrightlite said:
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
Click to expand...
Click to collapse
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.

dandrumheller said:
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
Click to expand...
Click to collapse
It feels not like a beta. It's more like a big bug fix with much patches. For example my Wifi is now stable as hell and never reconnections anymore. Hope it keeps stable, but looks very very good. I think this beta will be the final release in few months, or weeks? But it's much better than 7.0. And better than LOS14.1, which is not so stable (on my other phone). And I have no app crashes anymore. Gboard was crashing with 7.0 one time and few other apps like firewall. So, 7.1.1 is pure stable as hell and must have :laugh:

Afaik, it's not beta. It's​ soak. So, if test users reported as stable, it will be pushed to all as the final build. If not, Moto has to fixed and not all users around the world will be affected.
Regular and recommend way of releasing update.
Sent from my LG-V940n using Tapatalk

Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:

If you are on XT1635-03 with reteu frmware you will not receice any OTA. My experience told that you can't even sideload an update. So no worry about bricks.
Very often devices are hardbricked when you are downgrading bootloader but once I have hardbricked my Nexus 6 with OTA (sideloading it). Well, it was not full brick, but I can't load the system (only fastboot) and my bootloader was locked. Without system loaded you can't allow unlocking procedure so the first thing I do with new phone is unlocking.

allrightlite said:
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
Click to expand...
Click to collapse
I know the build is not a beta. I'm referring to the fact that once you leave the official upgrade path, taking any update is a scenario not tested by Moto. So you are testing for them. Maybe you win, maybe you brick.

It seems that the problem with "addison_retcn" may be fixed with editing build.prop but in this case systemless root is required (AFAIK there us no systemless root for Nougat)

Is it safe to flash April update image on May update to return to stock?

I'm currently on the May security update (NPN25.137-24.4) with TWRP and Magisk. I can't find the stock ROM for this update so I have no way to return to stock May update. Can I flash oem/boot/logo/recovery/system from the April update to "return" to the April update and take the OTAs that way?
I ask because I'm aware of the people downgrading to MM from Nougat and then taking OTAs bricking their device due to different bootloaders.

Afaik, downgrading to mm and then accepting ota will brick your device.
Wait for someone else to confirm.
Sent from my XT1635-02 using Tapatalk

hmmm. bump. the last stock rom before 7.1.1 is still not available anywhere.
To add onto this thread, why isn't there a 7.1.1 stock rom uploaded anywhere?

I bit the bullet and flashed the previous version to return to stock. It worked fine. Updating to 7.1.1.
Now... does anyone have a 7.1.1 stock image anywhere for me to be able to return to stock later? Whenever I try
fastboot boot twrp.img
It just locks up at the TWRP splash screen (using Alberto's twrp port, 3.1.1)

SAGExSDX said:
does anyone have a 7.1.1 stock image anywhere for me to be able to return to stock later?
Click to expand...
Click to collapse
there's still no image of 7.1.1 for the Addison, maybe in a few months
you can downgrade avoiding the gpt.bin and (I believe)the bootloader.bin, after that you can download the OTA file from the forum and install it, check the forum for more info

are you sure that's safe? I felt ok going from 7.0 may update to 7.0 april update cuz I was sure there wasn't a change in bootloader or anything. But going from 7.1 to 7.0 to take the OTA sounds like the exact same scenario as ppl who went from 7.0 to 6.0 and then bricked their device when taking OTAs.

Try this, although it's from Verizon but works for other devices as well without any issues.
"https://www.androidfilehost.com/?fid=673368273298982188"

ROM_HUNTER said:
Try this, although it's from Verizon but works for other devices as well without any issues.
"https://www.androidfilehost.com/?fid=673368273298982188"
Click to expand...
Click to collapse
Isn't that for the Moto Z, not the Moto Z Play?

SAGExSDX said:
Isn't that for the Moto Z, not the Moto Z Play?
Click to expand...
Click to collapse
Yeah, that's for Moto Z (griffin), you'll want ROMs labelled as addison for Moto Z Play.
No sign of a 7.1.1 fastboot stock ROM for Moto Z Play as of yet, from what I can see.

SAGExSDX said:
Isn't that for the Moto Z, not the Moto Z Play?
Click to expand...
Click to collapse
Yeah, my bad, this is the one for Addison.
"https://www.androidfilehost.com/?fid=889764386195928508"
'https://www.androidfilehost.com/?fid=673368273298986785"

Root Latest OTA Update (CRK1)

Samsung just put out a new update and the oreo rooting method listed on here fails at odin. Im wanting to root because i found some interesting things in the phone info app under secret codes. one of them was unlock kernel and a few others i wanted to check out but it seems its blocked so i need root to bypass the block. anyone know of how root can be achieved in this new update? THANKS

bjf189 said:
Samsung just put out a new update and the oreo rooting method listed on here fails at odin. Im wanting to root because i found some interesting things in the phone info app under secret codes. one of them was unlock kernel and a few others i wanted to check out but it seems its blocked so i need root to bypass the block. anyone know of how root can be achieved in this new update? THANKS
Click to expand...
Click to collapse
They blocked root on that update so you are now stuck on a non rootable device. Sorry

stang5litre said:
They blocked root on that update so you are now stuck on a non rootable device. Sorry
Click to expand...
Click to collapse
It's fine. I was gonna be rooted only for a short time just to check those things out. It sucks not having root but I'd rather not deal with the lag from the boot image if it worked on this update that is. Maybe someone will crack this update in time cause nothings unhackable.
So is downgrading possible still or does this update block downgrading to? I haven't tried yet but if you have then save me some time

bjf189 said:
It's fine. I was gonna be rooted only for a short time just to check those things out. It sucks not having root but I'd rather not deal with the lag from the boot image if it worked on this update that is. Maybe someone will crack this update in time cause nothings unhackable.
So is downgrading possible still or does this update block downgrading to? I haven't tried yet but if you have then save me some time
Click to expand...
Click to collapse
Yes, blocks downgrading, but you should be able to flash any other updated carrier firmware and the U version

stang5litre said:
They blocked root on that update so you are now stuck on a non rootable device. Sorry
Click to expand...
Click to collapse
lvpre said:
Yes, blocks downgrading, but you should be able to flash any other updated carrier firmware and the U version
Click to expand...
Click to collapse
What difference would it make flashing other carrier firmware over this one?

bjf189 said:
What difference would it make flashing other carrier firmware over this one?
Click to expand...
Click to collapse
The U firmware would remove the Verizon bloatware. For example, if you left Verizon and went to T-Mobile...the U firmware of T-Mobile firmware could be installed to get the full bands for LTE coverage available. But if you are on Verizon and happy, probably not worth the trouble.

Sprint Z2 Force running on MetroPCS not downloading updates

Hi there. I think what I'm having is a network issue but I'm not entirely sure yet. I was hoping some of the good folks here might be able to help me figure it out.
So I have used the steps (to the letter) from the post titled "Free Sprint Moto Z2 Force carrier unlock quick and painless" by @Jessoocaca. (Many thanks to you @Jessooca, I'm actually running MetroPCS! YAY!) But I'm running into a problem. Motorola keeps telling me to run an update, and I'm not entirely sure how to deal with it. It states that it was a Jan 2019 update, version OCXS27.109-48-15.
My question is this. I've read as much as I can about the update and what it entails. My bootloader is still unlocked, Magisk is still on my phone, TWRP is also still on my phone. Also, as this is the XTXT1789-03, the Sprint version, I'm not entirely sure what to even do about the update. Is it something I actually need?
In System it does say that I'm still on the Sprint software variant and the Sprint software channel. Is that something I can change in order to get the update? Would it require a different ROM?
Auuugghhh. *headdesk*
Please advise! I would be much much obliged. Thanks in advance.

Don't update since you are rooted and has TWRP.
Only update when you are fully stocked (no TWRP, no root)..
Monstroquodlucet said:
Hi there. I think what I'm having is a network issue but I'm not entirely sure yet. I was hoping some of the good folks here might be able to help me figure it out.
So I have used the steps (to the letter) from the post titled "Free Sprint Moto Z2 Force carrier unlock quick and painless" by @Jessoocaca. (Many thanks to you @Jessooca, I'm actually running MetroPCS! YAY!) But I'm running into a problem. Motorola keeps telling me to run an update, and I'm not entirely sure how to deal with it. It states that it was a Jan 2019 update, version OCXS27.109-48-15.
My question is this. I've read as much as I can about the update and what it entails. My bootloader is still unlocked, Magisk is still on my phone, TWRP is also still on my phone. Also, as this is the XTXT1789-03, the Sprint version, I'm not entirely sure what to even do about the update. Is it something I actually need?
In System it does say that I'm still on the Sprint software variant and the Sprint software channel. Is that something I can change in order to get the update? Would it require a different ROM?
Auuugghhh. *headdesk*
Please advise! I would be much much obliged. Thanks in advance.
Click to expand...
Click to collapse

Don't update since you are rooted and has TWRP.
Only update when you are fully stocked (no TWRP, no root)..
Monstroquodlucet said:
Hi there. I think what I'm having is a network issue but I'm not entirely sure yet. I was hoping some of the good folks here might be able to help me figure it out.
So I have used the steps (to the letter) from the post titled "Free Sprint Moto Z2 Force carrier unlock quick and painless" by @Jessoocaca. (Many thanks to you @Jessooca, I'm actually running MetroPCS! YAY!) But I'm running into a problem. Motorola keeps telling me to run an update, and I'm not entirely sure how to deal with it. It states that it was a Jan 2019 update, version OCXS27.109-48-15.
My question is this. I've read as much as I can about the update and what it entails. My bootloader is still unlocked, Magisk is still on my phone, TWRP is also still on my phone. Also, as this is the XTXT1789-03, the Sprint version, I'm not entirely sure what to even do about the update. Is it something I actually need?
In System it does say that I'm still on the Sprint software variant and the Sprint software channel. Is that something I can change in order to get the update? Would it require a different ROM?
Auuugghhh. *headdesk*
Please advise! I would be much much obliged. Thanks in advance.
Click to expand...
Click to collapse

Will I have device issues if I don't update?
Also will I lose service if I unroot and re-lock my bootloader?

Monstroquodlucet said:
Also will I lose service if I unroot and re-lock my bootloader?
Click to expand...
Click to collapse
Just run an official flash all, reboot, take update and reroot. No reason to relock.