Downgrade from Pie to Nougat - Moto G5 Plus Questions & Answers

I already tried to downgrade from Pie to Los 14.1.
But RIL does not work after Installation. So I probably missed something.
I think i need N Firmware first, right?
So how to downgrade correctly?
Thanks in advance!

Depends on the firmware you were prior to flashing pie. You can fastboot flash according to that. Or just get a TWRP flashable stock build of nougat.

Grab the latest nougat from this thread:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The versions that use the aroma installer will make sure that you retain your IMEI by fixing your persist permissions.

Related

Flashing Nougat with TWRP without losing TWRP

Hi, newbie question here. I just got my Axon 7. Unlocked the bootloader. Installed TWRP. Made full nandroids of stock and rooted firmwares.
I would like to flash the new Nougat update. What would be the best way to accomplish this without losing TWRP? and what is the correct firmware to use? ota? Also can nougat be rooted? Just dont want to brick my new phone. Thanks
No TWRP flashable file yet.....but I'm sure it'll be soon.
You will need to be on the Nougat bootstack, but you'll have to search for that info.

NFC not working on custom oreo rom

Hello
I've been struggling with this issue for weeks now. I have literally tried everything.
I have a A2017G with the universal B32 oreo bootstack from NFound. I've tried clean AEX and Resurrection Remix. Various builds. I have wiped system, data, cache, internal before trying to flash another rom. I have tried using different packages of GAPPS 8.1 ARM64 (Nano, Pico, Aroma). I've tried formatting data to f2fs and ext4. I've tried with and without supersu and Magisk.
My NFC module is not broken, I put it on B09 stock and it worked perfectly fine. It could read my NFC card. But as soon as I install either AEX or Resurrection Remix it just stays grayed out. But my NFC service keeps running for some reason and drains my battery. I seem to be the only person having this as well, not a single person running the same builds has these issues.
I ended up giving up and just deleted the NFC.apk from /system/data to fully disable NFC so it would stop draining my battery.
I'd really appreciate some help if any of you has a solution for this. I used to use my NFC all the time for payments.
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
AnonVendetta said:
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
Click to expand...
Click to collapse
Do you reflash a different bootstack or do you just keep the stock one?
g0dzstar said:
Do you reflash a different bootstack or do you just keep the stock one?
Click to expand...
Click to collapse
You can't keep the stock bootstack lol, use the one that the ROM recommends. Univ bootloader + X modem for Nougat, univ B32 bootstack for Oreo
Choose an username... said:
You can't keep the stock bootstack lol, use the one that the ROM recommends. Univ bootloader + X modem for Nougat, univ B32 bootstack for Oreo
Click to expand...
Click to collapse
He wasn't very specific xD. I've already tried a lot so I wouldn't be surprised if this would fix it. But I will try going back to stock and OTA'ing to B32 and try again.
AnonVendetta said:
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
Click to expand...
Click to collapse
This solution actually worked. Thank you very much!
AnonVendetta said:
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
Click to expand...
Click to collapse
Hi, is it possible to provide me the files for a A2017G. I have the same problem with a RR Oreo ROM.
cybertronicx said:
Hi, is it possible to provide me the files for a A2017G. I have the same problem with a RR Oreo ROM.
Click to expand...
Click to collapse
You can get them yourself ? no need to be babysitted for everything. Go to the EDL Tool thread (google "edl tool") and download an A2017G file, and install it with EDL Tool
@cybertronicx: Sorry but no, I have an A2017U, not G, so there is no reason I would keep the G firmware files hanging around. I wouldnt be able to flash them anyway. The B19 EDL I downloaded is from a thread by @jcadduono, and he specifically states that the files he provides are for U only, and also warns not to try them on other variants.
AnonVendetta said:
@cybertronicx: Sorry but no, I have an A2017U, not G, so there is no reason I would keep the G firmware files hanging around. I wouldnt be able to flash them anyway. The B19 EDL I downloaded is from a thread by @jcadduono, and he specifically states that the files he provides are for U only, and also warns not to try them on other variants.
Click to expand...
Click to collapse
That's BS though. Flashing the corresponding modem and TWRP just after flashing the edl rom makes it usable on other variants.
Let's keep the thread simple though
@Choose an username...: Flashing a G firmware on a U model in EDL mode would really work? I had no idea, I thought it would hardbrick the phone for sure. On most other Android devices, flashing another firmware, even from a different variant of the same device, will result in bricking. But the A2017U has the best official and community support vs A2017G and A2017 (China).
AnonVendetta said:
@Choose an username...: Flashing a G firmware on a U model in EDL mode would really work? I had no idea, I thought it would hardbrick the phone for sure. On most other Android devices, flashing another firmware, even from a different variant of the same device, will result in bricking. But the A2017U has the best official and community support vs A2017G and A2017 (China).
Click to expand...
Click to collapse
I'm writing off of an U ROM on a G. Of course it can be made. There are a bunch of guides around the forum, that tell you how to do this.
The thing is, all of these phones are ailsa_ii. I know you are talking about variants as in thea/titan for the Moto G2, but in those cases they had 4g on the thea and 3g on the titan for example. In this case the phones only vary in the modem used. If you flash the U ROM as-is, it will probably boot, but you won't have cell signal at all.

Bootloader and modem question

How do I know which bootloader do I have? I'm currently running build B35.
Can someone direct me to a thread how to flash universal bootloader and modem?
If I use bkores flash toolkit, it said you have to flash universal bootloader, modem along with Rom and Gapps but in which order?
If using twrp for future flash do I need to flash universal bootloader and modem every time I switch ROM?
I'm not an expert but here's what I understand.
1. You don't have to worry which version you have unless you're flashing a custom ROM, usually for Nougat you want the B15 and for Oreo you want the B35.
2.Universal Bootloader>Modem>ROM>GApps>Magisk/SuperSU
3.You only need to flash it once if you're switching ROMs with the same android version.
Nicz14 said:
I'm not an expert but here's what I understand.
1. You don't have to worry which version you have unless you're flashing a custom ROM, usually for Nougat you want the B15 and for Oreo you want the B35.
2.Universal Bootloader>Modem>ROM>GApps>Magisk/SuperSU
3.You only need to flash it once if you're switching ROMs with the same android version.
Click to expand...
Click to collapse
Thank you for the reply.
I'm on Android 7.1.1 with build B35.
I want to flash a custom ROM.
vic_singh said:
Thank you for the reply.
I'm on Android 7.1.1 with build B35.
I want to flash a custom ROM.
Click to expand...
Click to collapse
If you haven't you need to unlock your bootloader before you can start flashing custom ROM. You can find a guide on how to do it here.

Downgrade to 5.1 lollipop

If i use twrp to flash device back from nougat to lollipop (stock), will be any chance in a future to install original updates (OTA?)
No!
How to do it? I have official Nougat. I've unlocked bootloader and installed twrp.
I've tried twrp, but can not find debloated flash rom. Some of guys are making downgrade with fastboot over youtube, but they downgrade back only previous version of android, for example from nougat to marshmallow, or from marchmallow to lollipop.
|
What will happen, if i try with fastboot way? Will I brick the phone?

Can I downgrade to Nougat (Android 7) if I installed the Oreo update?

if so, which version or file should I use?
thanks in advance.
@josuemf: Downgrading is easy peasy, no issues at all. You can even go all the way back to Marshmallow if you want. Just flash a stock ROM EDL of your choice.

Categories

Resources