Develop Bugs

Prob dumb question

Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!

ryanbmw51 said:
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
Click to expand...
Click to collapse
Pretty sure stock recovery and no root is required to take the OTA. Best bet is to just flash the newest factory image and start over with root etc.

ryanbmw51 said:
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
Click to expand...
Click to collapse
You have unlocked bootloader, flashed custom software and now you are worried about some security patch.

Not worried. At all. As I said I'm happy with my setup. Problem is how can I make the notification go away? It keeps coming back.

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)

Want to downgrade from Android Oreo to Nougat

After having upgraded from Nougat 7.1.1 to Oreo using the OTA update I'm not feeling the love for it and it breaks a few thing I need to work.
Can anybody point me in the direction of a guide that works to perform the downgrade ? I'm really attached to my Moto Z Play and I don't want to brick it .

Is your bootloader unlocked?

rampare99 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No it isn't but I don't see any challenge in unlocking it. Having said that I'm starting to come around to liking Oreo on the Moto.

Iceworkz said:
No it isn't but I don't see any challenge in unlocking it. Having said that I'm starting to come around to liking Oreo on the Moto.
Click to expand...
Click to collapse
I'm glad to hear that. If you still want to go back to Nougat you'd need to unlock your bootloader, flash TWRP and then flash this zip (after a factory reset) from shamu17:
https://androidfilehost.com/?fid=889964283620776181
And that's it. If you want to go back to Oreo, you'll need to flash shamu17's Oreo rom.

The only thing I'm noticing since going to Oreo on my Z Play is apps will download to 100% from the Play store but wont install unless I swipe away app from recent apps. Already cleared cache and all that but still goes back to not installing apps. Annoying.

I'd suggest just installing official LineageOS 14.1

Chase down @SupahCookie and guide.

also my guide
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530

Iceworkz said:
After having upgraded from Nougat 7.1.1 to Oreo using the OTA update I'm not feeling the love for it and it breaks a few thing I need to work.
Can anybody point me in the direction of a guide that works to perform the downgrade ? I'm really attached to my Moto Z Play and I don't want to brick it .
Click to expand...
Click to collapse
Don't feel bad. After I got the Oreo update, all my weather and clock widgets stopped working. They are either frozen in time, or completely invisible on my home screen. My phone ran smooth as silk on Nougat, so I'm less than happy with this new operating system.

use the "alternative"
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530

Downgrading from Pie to Oreo

Hi everyone!
I've updated my z2 force to pie, and i wish I hadn't. Is it possible to downgrade back to Oreo and how? If possible, i wouldn't want to loose my gpay/banking apps, so i presume I'd have to relock the bootloader after downgrading. Sorry, newb here.
Thanks.

crnispot said:
Hi everyone!
I've updated my z2 force to pie, and i wish I hadn't. Is it possible to downgrade back to Oreo and how? If possible, i wouldn't want to loose my gpay/banking apps, so i presume I'd have to relock the bootloader after downgrading. Sorry, newb here.
Thanks.
Click to expand...
Click to collapse
Based on all of the things that have happened over the last couple of weeks with several users in this forum, it appears that there is no going back to Oreo from Pie. Once you have installed a Pie modem, so far, no one had come up with a way to get an Oreo modem back in the device and get one working. There may be hope in the future but it hasnt been worked out yet.

Hot tip, If you lock you bootloader after flashing Oreo and can no longer enable OEM Unlock as you cannot access internet... use Bluetooth Tether to other phone to access internet, then OEM Unlock is available again.

Rooted ATT G8 on Android 10 - Update to Android 11?

I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it

BWA_Dallas said:
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
Click to expand...
Click to collapse
So, if it's rooted, you won't get an update, or rather you won't be able to apply it. So it won't 'break' root, it just won't happen.
Sure, just crossflash to the newer rom, it has no effect on root. Doing so doesn't affect root, it will stay exactly as it was prior to crossflashing.

BWA_Dallas said:
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
Click to expand...
Click to collapse
Forgot you're using an at&t rom, and those kdz aren't available. So, choices, go to an 'open' rom, which should have much of the at&t functionality, but maybe not all. Or, re lock the boot loader, do the update ota, and then root it again.
Be careful though, to relock a boot loader the rom has to be completely stock, no mods whatsoever.
personally, I'd just go with one of the 'open' roms... and I'd never use at&t lol, but that's just me.

AsItLies said:
Forgot you're using an at&t rom, and those kdz aren't available. So, choices, go to an 'open' rom, which should have much of the at&t functionality, but maybe not all. Or, re lock the boot loader, do the update ota, and then root it again.
Be careful though, to relock a boot loader the rom has to be completely stock, no mods whatsoever.
personally, I'd just go with one of the 'open' roms... and I'd never use at&t lol, but that's just me.
Click to expand...
Click to collapse
Do you have a particular open rom you recommend?

BWA_Dallas said:
Do you have a particular open rom you recommend?
Click to expand...
Click to collapse
LG G820QM(LMG820QM) aka LG G8 ThinQ - LG-Firmwares.com
LMG820QM download the firmware for free! Detailed installation instruction. Video review of the model and its features. User feedback and latest news.
lg-firmwares.com
I'd suggest the USA version, it's the us open, should have all the functionality for all the carriers, minus the bloatware.
Except for one thing, some carriers, like at&t, have in the past, not sure if they still do, limit things like volte ability to just their phones / roms.
that, and because they don't make their kdz available, I would never use them.