Related
Since I've been lurking all day looking for solutions, I thought I'd share my success story and instructions. I'm a new poster so I can't make links, so I'll do my best to give you an idea if you've got the right link. The fastboot instructions may be a little truncated, so look around if they seem unclear. These are the commands you need to enter, though. I wasn't able to relock my bootloader.
This is for the Consumer Cellular Moto G 2014 X1064. Starting from retail (where you have the Consumer Cellular app):
Unlock the bootloader on Moto's site at motorola-global-portal.custhelp dot com
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder (I was using a Mac with the quick fastboot/ADB tools and just typed them in Terminal):
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader. No Consumer Cellular app.
Grab the torrent file from the thread titled "[OTA] Moto G 2014 XT1064 v22.11.6" on this subforum. It's on page 8, post #73
Rename that file to something simple like update.zip
Use Android File Transfer or similar (I had a Mac) to put that on the root of your device. It was at the same level as the Downloads folder. If you can see that, you're in the right place.
Reboot into fastboot mode
Select recovery mode (press volume down to highlight it, then volume up to select)
You'll now see an Android guy with a red triangle. Press volume up and power at the same time, let go, and you should be in another text menu.
Select boot from SD card (use volume down to highlight it, then power to select)
Select your update.zip
Wait 20 minutes or so while it works
Select reboot when you're finished
That was enough to get me to Android 5. Good luck everyone!
Janus Kirin said:
Since I've been lurking all day looking for solutions, I thought I'd share my success story and instructions. I'm a new poster so I can't make links, so I'll do my best to give you an idea if you've got the right link. The fastboot instructions may be a little truncated, so look around if they seem unclear. These are the commands you need to enter, though. I wasn't able to relock my bootloader.
This is for the Consumer Cellular Moto G 2014 X1064. Starting from retail (where you have the Consumer Cellular app):
Unlock the bootloader on Moto's site at motorola-global-portal.custhelp dot com
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder (I was using a Mac with the quick fastboot/ADB tools and just typed them in Terminal):
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader. No Consumer Cellular app.
Grab the torrent file from the thread titled "[OTA] Moto G 2014 XT1064 v22.11.6" on this subforum. It's on page 8, post #73
Rename that file to something simple like update.zip
Use Android File Transfer or similar (I had a Mac) to put that on the root of your device. It was at the same level as the Downloads folder. If you can see that, you're in the right place.
Reboot into fastboot mode
Select recovery mode (press volume down to highlight it, then volume up to select)
You'll now see an Android guy with a red triangle. Press volume up and power at the same time, let go, and you should be in another text menu.
Select boot from SD card (use volume down to highlight it, then power to select)
Select your update.zip
Wait 20 minutes or so while it works
Select reboot when you're finished
That was enough to get me to Android 5. Good luck everyone!
Click to expand...
Click to collapse
During the first flash, did you not get System Downgrade errors? And after reboot i could still see same Consumer Cellular system version. Did you verify your system version before you updated Lollipop?
I still cant believe it worked for you as i have seen other people still having issues like me where they cannot flash 21.11.17 version because of system not permitting downgrading.
Please add any more insights or if you downloaded the ROM from somewhere else.
Thanks.
zoomingrocket said:
During the first flash, did you not get System Downgrade errors? And after reboot i could still see same Consumer Cellular system version. Did you verify your system version before you updated Lollipop?
I still cant believe it worked for you as i have seen other people still having issues like me where they cannot flash 21.11.17 version because of system not permitting downgrading.
Please add any more insights or if you downloaded the ROM from somewhere else.
Thanks.
Click to expand...
Click to collapse
I didn't get system downgrade errors, no. I unlocked first. Maybe that was it?
My system version was 21.11.23.titan_ccaws.AWSCC.en.US cc
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Janus Kirin said:
I didn't get system downgrade errors, no. I unlocked first. Maybe that was it?
My system version was 21.11.23.titan_ccaws.AWSCC.en.US cc
Click to expand...
Click to collapse
That's the same version I had, and I got the same error as the person above.
chibichn said:
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Click to expand...
Click to collapse
I was not able to lock the bootloader. It shows that warning for five seconds and then starts the boot animation. I'd also like to lock it, but I've decided not to press my luck.
Janus Kirin said:
I was not able to lock the bootloader. It shows that warning for five seconds and then starts the boot animation. I'd also like to lock it, but I've decided not to press my luck.
Click to expand...
Click to collapse
chibichn said:
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Click to expand...
Click to collapse
Thanks a ton Janus & Chibichn, it works and i was able to downgrade and flash Lollipop via recovery!
See this post:
http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Seems to work for me. Happily running Lollipop on my Consumer Cellular G (2014).
Other than the void warranty, any other disadvantage in unlocking the bootloader? Will we get future OTA updates or well have to flash every time?
Thanks, worked for me, for those who aren't able to downgrade, are you sure you got your bootloader unlocked?
Great tutorial, worked exactly as described. Thanks A LOT! Now to root and start restoring my TitaniumBackup.
Thanks for the tutorial, I am having issues on step 14 the installation aborts in recovery. I did rename the zip to update.zip. If some one can point me in the right direction that would be appreciated. Thanks.
Sent from my A0001 using XDA Free mobile app
Thanks a ton for this. Got my less than 24 hour old Moto G upgraded last night. Youre a lifesaver.
root??
work was actually really really perfect! however I noticed that when starting this root and lost without recovery. is normal in this version? because at the end she asked me to reinstall it would root.
I got the xt1064 from consumer cellular and have been trying to replicate the process but with a locked bootloader.
My cc x1064 originally came with 21.11.23.titan_ccaws.AWSCC.en.US cc. I couldn't flash an older US retail build (21.11.17.titan_retuaws.retuaws.en.US - the latest available for download at the time) because of downgrade issues. Locked bootloader wont let you downgrade, image verification issue.
As of today I was able to located the latest US retails aws rom for 21.11.23. I ended up getting it from a different faster mirror than the ones posted in another xda thread.
http://motofirmware.com/files/file/951-retuaws-xt1064-444-kxb2185-23-cid9-cfcxmlzip/
Fastboot flash of this rom was successful. No bootloader/image issues. My consumer cellular rom was removed, cc app was gone, and now my system version reads 21.11.23.titan_retuaws.retuaws.en.US cc ( build # kxb21.85-23). Don't know why the "cc" is still appended to the end of the system version. Baseband version also had CCAWS_CUST in it. Is this an indication that consumer cellular components like the baseband modem files were untouched during the US retail flash?
Anyway, tried all the tutorials on getting OTA to update via stock recovery thru "update form sd" but the update keeps failing. I keep getting message " package expect build finger print of motorola/titan_retuaws/titan_umts:4.4.4/kxb21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan_retuaws/titan_umts:4.4.4KXB21.85-23/30:u Installation aborted."
So the phone is complaining that the package currently installed either had to be 21.85-17 (4.4.4) or lollipop 5.0, in order to flash , but found 21.85-23(4.4.4) on my phone instead, hence it fails because of version mismatch. So in order to update OTA lollipop with a locked bootloader only a currently installed build of 21.11.17 will allow you to do it? If that is the case, I can't downgrade and thus can update the OTA.
diamondjoker5 said:
I got the xt1064 from consumer cellular and have been trying to replicate the process but with a locked bootloader.
My cc x1064 originally came with 21.11.23.titan_ccaws.AWSCC.en.US cc. I couldn't flash an older US retail build (21.11.17.titan_retuaws.retuaws.en.US - the latest available for download at the time) because of downgrade issues. Locked bootloader wont let you downgrade, image verification issue.
As of today I was able to located the latest US retails aws rom for 21.11.23. I ended up getting it from a different faster mirror than the ones posted in another xda thread.
http://motofirmware.com/files/file/951-retuaws-xt1064-444-kxb2185-23-cid9-cfcxmlzip/
Fastboot flash of this rom was successful. No bootloader/image issues. My consumer cellular rom was removed, cc app was gone, and now my system version reads 21.11.23.titan_retuaws.retuaws.en.US cc ( build # kxb21.85-23). Don't know why the "cc" is still appended to the end of the system version. Baseband version also had CCAWS_CUST in it. Is this an indication that consumer cellular components like the baseband modem files were untouched during the US retail flash?
Anyway, tried all the tutorials on getting OTA to update via stock recovery thru "update form sd" but the update keeps failing. I keep getting message " package expect build finger print of motorola/titan_retuaws/titan_umts:4.4.4/kxb21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan_retuaws/titan_umts:4.4.4KXB21.85-23/30:u Installation aborted."
So the phone is complaining that the package currently installed either had to be 21.85-17 (4.4.4) or lollipop 5.0, in order to flash , but found 21.85-23(4.4.4) on my phone instead, hence it fails because of version mismatch. So in order to update OTA lollipop with a locked bootloader only a currently installed build of 21.11.17 will allow you to do it? If that is the case, I can't downgrade and thus can update the OTA.
Click to expand...
Click to collapse
I also noticed that Base Band version stays from Consumer Cellular. Any idea if we should or can flash the Base Band to US Retail? Also as far i read, yes the lollipop update is based on top of 21.11.17 not 21.11.23. There may be a lollipop image on top of 21.11.23 but i am not sure.
^^ personally I didn't care to void the warranty since I picked it up for 75 (gift card for another 75), also the consumer cellular model. Updated it to 5.0 and using it as my spare phone for browsing and web on my secondary line, it works fine. Immediately after the update, getting back into recovery is an issue, haven't tried since but it's been working fine so I'm not complaining.
zoomingrocket said:
I also noticed that Base Band version stays from Consumer Cellular. Any idea if we should or can flash the Base Band to US Retail? Also as far i read, yes the lollipop update is based on top of 21.11.17 not 21.11.23. There may be a lollipop image on top of 21.11.23 but i am not sure.
Click to expand...
Click to collapse
I was successful with the Consumer Cellular XT1064, but I unlocked the bootloader first and left it that way. It is my understanding that this is required to downgrade, but I'm no expert.
The Lollipop *does* update the Baseband, though the CCAWS_CUST was/is appended throughout. Unsure what that is all about (or if it even relates to Consumer Cellular), but it works just fine. I'll paste the various Baseband, System, and Build numbers reported as I progressed below. Perhaps this will shed some light?
___________________________________
Consumer Cellular XT1064 - As found:
Baseband: MSM8626BP_1032.394.88.00R, CCAWS_CUST
System: 21.11.23.titan_ccaws.AWSCC.en.US.cc
Build: KXB21.85-23
___________________________________
After factory retail flash:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
Baseband: MSM8626BP_1032.394.88.00R, CCAWS_CUST
System: 21.11.17.titan_retuaws.retuaws.en.US na
Build: KXB21.85-17
___________________________________
After Lollipop update via adb sideload:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip
Baseband: MSM8626BP_1032.3105.93.00R, CCAWS_CUST
System: 22.11.6.titan_retuaws.retuaws.en.US cc
Build: LBX22.39-6
___________________________________
Kinda strange that the System went from US cc, to US na, then back to US cc. ???
If someone can provide this information from another carrier or carrier-less, it would be interesting to compare. I have 2 more of these ordered and due to arrive Wednesday. I'll check back here before I alter them in case someone wants additional info. - Regards
---------- Post added at 02:48 AM ---------- Previous post was at 02:07 AM ----------
chibichn said:
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Click to expand...
Click to collapse
Oh my, that bat file looks eerily familiar to me. Could be a coincidence, but I *know* Jack - very well
Recovery issue
Anyone else have issues getting back into recovery after flashing lollipop? Before I wipe mine and redownload the file, is anyone else's recovery an issue? I get stuck at the dead android logo and it won't show the recovery menu text/options.
By chance will this by default carrier unlock the device as well?
Hi,
I have a complete stock moto g4 plus XT1642, with firmware build number NPJS25.93-14-4 (march security update), retgb.
I didn't get the June security update, and I the phone insists that my software is up to date..
I am not interested in rooting my phone. How can I force it to update?
(I also have the same problem with another retgb moto g4 non-plus..).
Thanks!
Yeah, retgb updates seem to be taking a little while to deploy... Like your experience, I was waiting for updates on the retgb channel too... Then I updated using the captured updates on XDA, which appeared to have worked okay
You've got 2 routes:
1) You can download the June 2017 OTA update from here to your device: https://drive.google.com/drive/folders/0B-GUyOfb8OgzR1VrQ1NHWDVmWE0
This is the same update that was on XDA, just mirrored to my Google Drive as the original link does not appear to work.
File name:Blur_Version.25.201.4.athene.retail.en.US.zip
Size: 56 MB
md5 checksum: 4ce250195b2eb71c960ec3b6579bc9d0
Ensure your device is fully updated to NPJS25.93-14-4 (bootloader should be version B1:05), you have a stock recovery, unmodified system and baseband (baseband version should end in .62R), as this update requires the March 2017 update. If your bootloader is still locked, this should all be applicable. Then:
Boot to stock recovery (notes on how to access stock recovery are here: https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58 )
Select 'apply update from SD card'
Locate the Blur_Version.25.201.4.athene.retail.en.US.zip on your device
Install update.
You may wish to wipe cache before rebooting.
Now, you should be updated to June 2017. There's also the September 2017 OTA (requiring the June 2017 patch) which you can apply in the same fashion: https://forum.xda-developers.com/moto-g4-plus/how-to/captured-ota-september-security-patch-t3680367
I successfully flashed the June 2017 OTA onto my XT1642, retgb (so same as yours) that had previously been running on NPJS25.93-14-4 and have had no issues - my network provider, 3 UK, works well
2) If you want to, you can jump straight to the September 2017 stock build, which is running on my XT1642, and this is the method I chose to update (as I was rooted too, so needed a near clean start). I think it should be suitable for the Moto G4 too that you have, but you may wish to check the following stock ROM thread to confirm.
a) Download the September 2017 stock ROM (NPJS25.93-14-10): https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
b)Set up ADB as directed in the above post. Extract the ROM files in the same folder as your ADB terminal (so you should see files like oem.img and bootloader.img mixed with adb.exe and fastboot.exe)
c)If you wish to keep your data and do not need to re-lock your bootloader (i.e. your bootloader is already locked, or unlocked) and are simply updating, you could use the following fastboot commands to keep your data intact. Back up your data just in case your system becomes unstable and needs a factory reset, though I did not notice any corruption of my data. The initial boot was a little slow (presumably to rebuild caches and update links as necessary):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should update your GPT, bootloader, recovery, system and modem to NPJS25.93-14-10, Sept 2017 patch. Though you could edit one of the flashing scripts - provided in the stock ROM thread - to match the above commands, I preferred to manually copy each command and execute the commands, checking each command flashed. As with anything affecting the firmware of your device, take your time in flashing. Using the September 2017 stock ROM, my XT1642 is still running happily with the September security patch (and seems smoother too )
Bear in mind that with the June and September updates, the bootloader is updated to version B1:06. Thus, it makes downgrading risky. From the sounds of it, you're not interested in rooting/downgrading, so this might not be for you anyway. Just a heads up that downgrading from the June or September 2017 stock ROMs (e.g. by flashing the older stock ROM without flashing GPT/bootloader) and then accepting OTA updates may cause a device to hard brick. We have ways of attempting to rescue a device in this state but I really wouldn't like to try them if at all possible.
Good luck whichever route you choose
I have two Moto G5 Plus. One has the npn25.137-93 build number and RETUS software channel. On the other one, I installed the stock firmware downloaded from:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
and now it displays: npn25.137-92 as build number and RETUS as software channel.
The phone with npn25.137-92 works perfectly, but it is not getting any updates to the the Jannuary 2018 security patch (npn25.137-92-4). The phone with npn25.137-93 has an update notification for the Jannuary 2018 security patch (npn25.137-93-4).
Can anyone explain me what's going on with the update notifications?
What is the different between npn25.137-92 and npn25.137-93?
Thanks!
The difference in notifications is likely due to one of your devices having the incorrect build for that software channel.
As far as I recall:
NPN25.137-92 was a build deployed to India, Latin America and possibly other regions.
NPN25.137-93 was deployed to EU, Asia Pacific and the US.
As such, one of your devices, the NPN25.137-93 device, is on the expected build for the retus software channel and is likely recognised by the Motorola servers, hence it's being served an OTA build. However, your other device, on the NPN25.137-92 firmware, is on a build that is not deployed to the retUS channel, and as such, the Motorola servers may not issue an OTA build (else issuing builds to devices on the wrong firmware for that sofware channel may cause a lot of issues), regardless of if the device still functions okay.
I'm not aware of significant differences between -93 and -92, except a different kernel build date and the different deployment of the updates. I'm hoping that you can flash the NPN25.137-93 or NPNS25.137-93-4 firmwares (or newer US specific firmwares) to get you back onto OTA updates, but we've seen that cross flashing firmwares can be risky. It's up to you if you wish to try to crossflash to get back onto the correct firmware, or just manually update the device on NPN25.137-92.
As an aside, this illustrates why it's important to check what firmware build is correct for your device. A useful method is to check reddit (https://www.reddit.com/r/MotoG/ ) or other XDA threads for what OTA updates are being received by a particular region before flashing any firmware (e.g. this thread https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-patch-november-npn25-137-92-t3718976 ). If users are receiving a particular latest OTA update for the US, it's a good pointer for what build you should be looking to flash.
Thanks for the detail explanation.
I would definitely like to go back to npn25.137-93. However, I am having a bad time finding that firmware. I checked:
- https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
- https://www.getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated/
- https://mirrors.lolinet.com/firmware/moto/potter/official/
but npn25.137-93 or npns25.137-93-4 for XT1687 (retus, carrier unlocked) is not where to be found.
I just noticed that POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml has been uploaded here: https://forum.xda-developers.com/g5-plus/help/rare-firmware-asia-t3753798
I downloaded it and at a first look it appears to be the complete firmware, so it can be easily flashed with fastboot. However, OP says it's for Asia, so I am not sure...
I am in same boat. Was NPN25.137-93 RETUS but ended up flashing NPN25.137-92 via ADB after trying to update and bricking phone. Now not receiving OTA. I have found some patches but no full firmware for RETUS. Wonder if anyone has TWRP backup that could be restored to get back on track to receive OTA updates?
omino said:
Thanks for the detail explanation.
I would definitely like to go back to npn25.137-93. However, I am having a bad time finding that firmware. I checked:
- https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
- https://www.getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated/
- https://mirrors.lolinet.com/firmware/moto/potter/official/
but npn25.137-93 or npns25.137-93-4 for XT1687 (retus, carrier unlocked) is not where to be found.
I just noticed that POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml has been uploaded here: https://forum.xda-developers.com/g5-plus/help/rare-firmware-asia-t3753798
I downloaded it and at a first look it appears to be the complete firmware, so it can be easily flashed with fastboot. However, OP says it's for Asia, so I am not sure...
Click to expand...
Click to collapse
Yeah, seems that no one has captured the NPN25.137-93 firmware, which is odd given the NPN25.137-92 firmware has been out for a while.
The build numbers for Asia and retUS and retEU appear to be the same (all NPNS25.137-93-4 from the various user reports from each region, e.g. https://forum.xda-developers.com/showpost.php?p=75645812&postcount=34 ) Also, looking at that stock ROM descriptor:
1)Build matches what you need.
2)Baseband matches that for the retUS OTA update for NPNS25.137-93-4 (though the baseband build is the same for NPNS25.137-92-4)
3)Build times for the kernel and this ROM are fairly close ( Tue Jan 23 17:26:00 for the stock ROM, kernel build date for the retUS OTA NPNS25.137-93-4 update is 17:40). Not conclusive, as the NPNS25.137-92-4 kernel got built at 11:31)
4)It's a Blur_Version retail.en.US firmware, which suggests it's for general release.
In summary, it looks like it should work. Of course, the only way to find out is to flash this firmware and hope... At least from the descriptor this looks to be an official firmware from Motorola. Good luck whatever you decide.
Code:
BUILD REQUEST INFO:
SW Version: potter-user 7.0 NPNS25.137-93-4 5 release-keysM8953_37.46.07.47R
MBM Version: C0.8C
Modem Version: M8953_37.46.07.47R
FSG Version: FSG-8953-07.75
Build Fingerprint: motorola/potter/potter:7.0/NPNS25.137-93-4/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.301.5.potter.retail.en.US
Model Number: Moto G (5) Plus
Android Version: 7.0
Baseband Version: M8953_37.46.07.47R
Build Id: NPNS25.137-93-4
SW Display Build ID: NPNS25.137-93-4
Build Date: Tue Jan 23 17:26:00 CST 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.301.5.potter.retail.en.US
Version when read from CPV: potter-user 7.0 NPNS25.137-93-4 5 release-keys
AB Update Enabled: False
Full Treble Enabled: False
echo92 said:
Yeah, seems that no one has captured the NPN25.137-93 firmware, which is odd given the NPN25.137-92 firmware has been out for a while.
The build numbers for Asia and retUS and retEU appear to be the same (all NPNS25.137-93-4 from the various user reports from each region, e.g. https://forum.xda-developers.com/showpost.php?p=75645812&postcount=34 ) Also, looking at that stock ROM descriptor:
1)Build matches what you need.
2)Baseband matches that for the retUS OTA update for NPNS25.137-93-4 (though the baseband build is the same for NPNS25.137-92-4)
3)Build times for the kernel and this ROM are fairly close ( Tue Jan 23 17:26:00 for the stock ROM, kernel build date for the retUS OTA NPNS25.137-93-4 update is 17:40). Not conclusive, as the NPNS25.137-92-4 kernel got built at 11:31)
4)It's a Blur_Version retail.en.US firmware, which suggests it's for general release.
In summary, it looks like it should work. Of course, the only way to find out is to flash this firmware and hope... At least from the descriptor this looks to be an official firmware from Motorola. Good luck whatever you decide.
Code:
BUILD REQUEST INFO:
SW Version: potter-user 7.0 NPNS25.137-93-4 5 release-keysM8953_37.46.07.47R
MBM Version: C0.8C
Modem Version: M8953_37.46.07.47R
FSG Version: FSG-8953-07.75
Build Fingerprint: motorola/potter/potter:7.0/NPNS25.137-93-4/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.301.5.potter.retail.en.US
Model Number: Moto G (5) Plus
Android Version: 7.0
Baseband Version: M8953_37.46.07.47R
Build Id: NPNS25.137-93-4
SW Display Build ID: NPNS25.137-93-4
Build Date: Tue Jan 23 17:26:00 CST 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.301.5.potter.retail.en.US
Version when read from CPV: potter-user 7.0 NPNS25.137-93-4 5 release-keys
AB Update Enabled: False
Full Treble Enabled: False
Click to expand...
Click to collapse
Man, your analysis was helpful and convincing. Thanks a lot!
I decided to pull the trigger and update. I confirm that it works fine on XT1687 on RETUS channel.
In case someone else wants to try, here is the process I followed:
1. Download POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from the link in: https://forum.xda-developers.com/g5-...-asia-t3753798
2. Unzip the archive
3. Open a cmd and cd to the POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml folder
4. Put the phone in bootloader mode (shutdown, then press volume down + power buttons at the same time until the phone turns on)
5. Execute the following fastboot commands (as per flashfile.xml):
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I did not erase userdata contrary to what is indicated in flashfile.xml, so I could keep my data. If you want to follow the process as per flashfile.xml, add the following command after erasing cache:
Code:
fastboot erase userdata
After flashing does about phone say RETUS or Asia?
Can confirm it worked for me as well. Thank you both!
Says Europe?
wayne-of3 said:
Says Europe?
Click to expand...
Click to collapse
Looks like the XT1687 has been tested and approved to be sold/used in the EU and the US, at least in terms of radios/electromagnetic radiation and electrical safety. https://www.cnet.com/news/certification-marks-decoded/
I'm not sure if it's important with regards to the firmware, as this build was deployed to the EU and Asia Pacific. All that info shows is that Motorola spent time testing and getting approval from the various safety agencies around the world. On my XT1642 (UK, G4 Plus - just for illustration), I see EU, US, Japan, Malaysia and Australia markings - a combination of where the device was sold and also shows me that I should be okay taking this device to those countries. If I went to the US, my device should not cause radio interference
The important things to look out for with flashing a stock ROM are:
1)Does your device function as expected?
2)Do you get OTA updates and do they install without issue?
If those two apply (we've already seen that 1) is true, 2) will have to wait for another OTA as the firmware is the latest as of writing), then you're likely on the correct build for your device.
Thanks for the clarification. Time will tell when next OTA comes around. Fingers crossed. Still feel better just having latest security.
Someone plz send full rom zip file for indian variant of moto g5 plus for jan security update
wayne-of3 said:
Thanks for the clarification. Time will tell when next OTA comes around. Fingers crossed. Still feel better just having latest security.
Click to expand...
Click to collapse
Have you gotten any OTA security patches since your flash your ROM?
dlong said:
Have you gotten any OTA security patches since your flash your ROM?
Click to expand...
Click to collapse
Yes, that got me back on track. That got me to April sp, but tired of waiting for updates so now on 7.1.2 lineage 14.
wayne-of3 said:
Yes, that got me back on track. That got me to April sp, but tired of waiting for updates so now on 7.1.1 lineage 14.
Click to expand...
Click to collapse
Thanks for the update. I have the same problem with mine which currently stuck on the Nov '17 patch/update/version. I'll have to do what you did. Thanks again.
omino said:
Man, your analysis was helpful and convincing. Thanks a lot!
I decided to pull the trigger and update. I confirm that it works fine on XT1687 on RETUS channel.
In case someone else wants to try, here is the process I followed:
1. Download POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from the link in: https://forum.xda-developers.com/g5-...-asia-t3753798
2. Unzip the archive
3. Open a cmd and cd to the POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml folder
4. Put the phone in bootloader mode (shutdown, then press volume down + power buttons at the same time until the phone turns on)
5. Execute the following fastboot commands (as per flashfile.xml):
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I did not erase userdata contrary to what is indicated in flashfile.xml, so I could keep my data. If you want to follow the process as per flashfile.xml, add the following command after erasing cache:
Code:
fastboot erase userdata
Click to expand...
Click to collapse
I had the exact same issue where I relocked my phone with npn25.137-92 and was stuck on Nov 2017 update. Following these steps worked like a charm. After flashing, I received both March and April system updates.
omino,
Thanks for posting the instructions. For others, I also followed the posted instructions and it works. I have a US - Retail, Unlock Moto G5 Plus (from Costco). I had some trouble finding the ROM archive; however, after finding it, the process worked. Note, that when I ran the fastboot commands, for each one, I got an error (or warning?) about "slot-count not found". A google search didn't yield any confirmed information on what it means. However, ignoring it and just continuing with all the commands, the results are fine. After each reboot, every 10 minutes or so it started informing me of new updates (March, then April, then finally June (or July?)). June/July, that's the last one. There doesn't seem to be one after that....
Has anyone else gotten a later security patch June or July for the G5 Plus for the NA RETUS RETAIL ?
I haven't got any update after the June security patch. I think the next one is the 8.1 update. But, as of today, I haven't seen it. Really a shame that Lenovo has not delivered Android 8.1 for NPNS25.137-93-14, RETUS channel.
Lenovo Sucks With Support / Continuing Support (Patches, etc.)
Yeah, pretty crappy of Lenovo. However, when I bought I my phone I wasn't even expecting security patches. Lenovo is very well known for not supporting their products after sale. Like new drivers for a newly released OS. For example, a laptop bought with Win7. But when Win10 comes out, they don't update the drivers so somethings do not work properly. You have to dig around looking at manufacturers and or just try other Lenovo laptop drivers and hope that one works. This phone was sort of a test phone. I would never buy a Lenovo for a daily driver since I don't expect Lenovo to support with security patches or fix bugs in their drivers. For my daily driver, I try to pick to pick LG and Samsung even if it's a entry-level or mid-level phone as I can not justify paying top-dollar for the high-end phones like the S9 or Note 8.
dlong said:
omino,
Has anyone else gotten a later security patch June or July for the G5 Plus for the NA RETUS RETAIL ?
Click to expand...
Click to collapse
Just as an FYI to myself. Today (October 23rd), Lenovo sent out the August security patch (Build number: NPNS25.137-93-18) for Moto G5 plus.
Hello to this amazing community,
I have recently tried for the first time to root my device.
Being unaware of the XDA community, I used this guy's guide - https://theunlockr.com/2016/11/29/root-motorola-moto-g4-moto-g4-plus/ .
As I went through the steps of unlocking, booting TWRP and installing superSU, I found out that the device won't start anymore, though the bootloader was still working at that point.
Unfortunately, that guide didn't emphasized the importance of first backing-up the system with TWRP.
Panicking, I even ended up wiping the entire device.
So I started my sisyphic journey of reviving the phone.
Being clueless of OEM stock versions etc. at this point, I thought that I should look for a fresh TWRP backup someone did after purchasing my exact Moto G4 Plus model - XT1644 so I ended up recovering the version that this dear guy has uploaded:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1644-stock-unmodified-6-t3536448
Happy as I was that the machine would finally start, I found out I was running an old Marshmallow version - exactly as the title says.
Still, I assumed that new OTA versions will be available and my device will be upgraded to the most up-to-date version.
Surprisingly for a rookie as me, checking for software updates showed " Your device's software is up to date".
So I search for a more up-do-date OEM stock version, and I have found the following version - NPJS25.93-14-13 here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I ran the bash file to flash the OEM while keeping the device unlocked.
The device has loaded finally with the familiar up-to-date version, and an available OTA update appeared.
I immediately ran the update.
That's when I first became familiar with the term "Brick". The device became completely dead.
Now, thanks to siddhesh9146 inceredible thread I managed to revive the device:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
I went through his steps, installed BlankFlash, flashed the latest gpt and bootloader and flashed version NPJS25.93-14-10.
The device will finally work! I would realize then, that the latest version is actually ATHENE_NPJS25.93-14-13 ,
And again, the device won't show any updates available.
So, finally, here are my questions:
1. What could I have done wrong in first place? Was it a wrong superSU version that caused the problem? (In case my rooting aspirations will return)
2. What caused the device to turn brick? I realize it has to do with downgrading version, but after I wiped the device, I only upgraded versions.
3. In general, when OTA are available? Only the newest stock version would receive OTA? Will I have to manually upgrade versions from now on?
4. Could I upgrade now to NPJS25.93-14-13 using the version that siddhesh9146 presented without wiping my entire phone? What exactly should I flash to do so?
5. What are the precautions I have to take while doing so? Is there a risk my phone will tun brick again?
Thanks!
Good to hear your device is working again, seems like it's been through a journey.
1)When you originally rooted, were you on stock Nougat (7.0)? If so, those rooting guides will not work and are likely for Marshmallow 6.0 systems only. What they fail to mention is that attempting to root whilst still on the stock Motorola Nougat kernel likely causes your device to not boot. The Nougat 7.0 stock kernel for our devices seems to be much stricter than the Marshmallow kernel when it comes to anti-rooting protections. Thus, we generally need to flash a custom kernel onto our devices before rooting - either with SuperSU or magisk. An example of a working guide for rooting on stock Nougat Moto G4/Plus is here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
2)Do you remember what the OTA you received was? I don't think there's an OTA for a build later than NPJS25.93-14-13 out yet. That suggests that the NPJS25.93-14-13 flash didn't work - did you check if the bash script reported [OKAY] after each command? By brick, do you mean the device had a blinking LED light, and there was no screen, and you were unable to boot to the bootloader and/or recovery? If the flash didn't work, then you may have taken a Marshmallow to Nougat OTA (NPJ25.93-14) which may have corrupted your device bootloader in the process.
3)OTAs are generally available for a particular build and for a particular software channel when they are released. For NPJS25.93-14-13, that's currently the latest build for EU/UK, Brazil and India devices, and there's word that there's a February 2018 OTA coming soon (no sign of it yet).
However, for your device (XT1644), if you are on the retUS - retail US - software channel, your device is on a different update path - NPJ25.93-14.7 would be the corresponding September 2017 patch for retUS software channel devices. NPJS25.93-14-10 is not one of the builds deployed to the retUS, and as such the Motorola servers may not issue you an OTA patch, regardless of whether the firmware would work. There have been reports of NPJS25.93-14-10 and NPJS25.93-14-13 working on US devices without issue, but you may not receive OTA updates.
You could manually update to NPJS25.93-14-13 using the OTA here, provided that you fully flashed the NPJS25.93-14-10 stock ROM (including GPT and bootloader, system, modem, boot, recovery, OEM, DSP, FSG). If you did not fully flash, you may be risking another hardbrick. https://forum.xda-developers.com/showpost.php?p=74973505&postcount=7
4)If you want to flash the NPJS25.93-14-13 stock ROM to be safe, or attempt to cross flash to the Sept 2017 NPJ25.93-14.7 firmware without wiping your data, you can use the following flashing commands. Be warned that you may have to factory reset if your device becomes unstable, so backup anyway. I would recommend manually flashing these commands:
a)copy and paste the first command to the ADB terminal
b)press enter, wait for [OKAY] to appear.
c) copy the next command, individually and in order, to the terminal, repeat b) and c) until you get to the end of the list.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands omit the fastboot erase userdata, preserving your data, and omit the OEM locking commands, which would lock your bootloader and erase your data in the process as well. Bear in mind that cross flashing can be risky, however, you may have to flash the NPJ25.93-14.7 update if you wish to receive OTA updates for the retUS software channel, if you are on that software channel. Link for the NPJ25.93-14.7 stock firmware if you wish to try: https://androidfilehost.com/?fid=817906626617945295
5)Generally, the main source of hard bricks I've noted has been users have been on stock Nougat (particularly the March 2017-latest) builds. They downgrade their device to stock Marshmallow firmware, which goes okay. However, in most - if not all - cases, their bootloaders are not downgraded, so you have a system and bootloader mismatch, with a newer Nougat bootloader but an older system than their bootloader patch level. For example, a B1:06 June 2017 patch level bootloader but a July 2016 Marshmallow system patch level.
The OTA checks that are performed are mainly on the system side i.e is your device on the July 2016 system patch? Are your system, OEM, recovery, boot etc. partitions unmodified and match the expected checksums for this OTA patch? If so, then install. However, in the updater script, there is no such check for the bootloader - the OTA updates appear to assume your bootloader is of the same patch level as your system. Normally, for a locked bootloader or for a user that has only updated their device, that assumption holds.
The issue we have here is that the system was downgraded to Marshmallow, so that assumption no longer holds. As the OTA updates are signed by Motorola, they have authorisation to write to your bootloader. That means this OTA can overwrite your bootloader, and if it's applying older code, can corrupt your newer Nougat bootloader and thus hard brick your device, which necessitates a blankflash to repair.
In other words, if you downgrade your device firmware, do not use or install OTA updates. If you do downgrade, only update with stock firmware that is as new or newer than your bootloader patch level. If your device is on the same patch level , then you should be able to use OTA updates. However as mentioned above, you need to be on the correct build for your device software channel as well to receive OTA updates from Motorola.
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
PartisanEntity said:
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
Click to expand...
Click to collapse
Problem; the procedure you followed is for a Moto G, and not a G5 Plus. If you used Moto G firmware on your Moto G5+, you may have induced more problems.
Moto g5+ firmwares are located at https://mirrors.lolinet.com/firmware/moto/potter/official/ Proper firmware for the Moto G5+ depends on your model and what country you are operating in.
potter - Moto G5 Plus = firmware
XT1680(LATAM/Argentina/Chile,2GB) {LATAM; Latin America}
XT1681(LATAM/Colombia/Mexico,2GB)
XT1683(Brazil,DS,DTV,2GB)
XT1684(Europe,3GB)
XT1685(Australia/NewZealand/Europe,3GB)
XT1686(India,3/4GB)
XT1687(USA,2GB/4GB)
{AMX, America Movil Mexico}{owns Claro}
{ATTMX; AT&T Mexico}
{AMZ; Amazon)
{RETAPAC; Retail Pacific; Australia, New Zealand}
{RETAR; Retail Argentina}
{RETBR; Retail Brazil}
{RETEU; Retail European Union)
{RETGB; Retail Great Britian}
{RETIN; Retail India}
{RETLA; Retail Latin America}
{RETMX; Retail Mexico}
{RETUS; Retail Unitied States}
{TEF, Telefonica S A.}
{TEFBR; Telefonica Brazil}
{TEFCO; Telefonica Columbia}
{TEFES; Telefonica European Sector}
{TEFMX; Telefonica Mexico}
Since your in Europe, your firmware group is probally RETEU, RETGB, or TEFES. You need to locate your model number of the phone, maybe a XT1684 or XT1685 and find the model number under the proper directory of firmware. I would download the latest, usually has 8.1.0_OPS28.85-17-6-2 in the firmware name and the lastest date. Extract the software and fastboot it.
For the 8.10_OPS28.85-17-6-2 firmwares the fastboot commands are:
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash modem NON-HLOS.bin
Fastboot flash fsg fsg.mbn
Fastboot flash dsp adspso.bin
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash system system.img_sparsechunk.4
Fastboot flash system system.img_sparsechunk.5
Fastboot flash system system.img_sparsechunk.6
Fastboot flash system system.img_sparsechunk.7
Fastboot flash system system.img_sparsechunk.8
Fastboot flash oem oem.img
Fastboot erase cache
Fastboot erase userdata
Fastboot erase DDR
Fastboot reboot
Again, this may not work because if the Moto G firmware you flashed on to the Moto G5+.....
Also, did LineageOS work on the phone before flashing Magisk and/or no-verity ?
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
PartisanEntity said:
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
Click to expand...
Click to collapse
Sorry to not reply earlier - was tied up with election recounts -----
Do not know what caused the boot loop. The proper way to install is to install LineagrOS first, boot LineageOS and make sure it comes up, Then go back to recovery/TWRP and install Magisk and the reboot to system and check LineageOS to make sure it came up. Then look in your apps and see if you have the Magisk icon. On the no-verity, I had a couple that did not work, I was turned on to Disable_Dm-Verity_ForcedEncrypt_02.04.2019.zip at
https://androidfilehost.com/?fid=11410963190603877244 (by WolfCity - thanks)
which worked for me. Use the procedure at paragraph 13 (my procedure that I listed
a PDF, its at http://s000.tinyupload.com/?file_id=...86655137330218 ) to install the program to decrypt the file system. Then reboot the phone and verify the phone is un-encrypted (it will say "Encrypt Phone" instead of Phone Encrypted). Then you will have to reboot back to recovery and reinstall Magisk again (its because when the file system was decrypted the memory was formatted/overwrited). Then boot back to system and verify Magisk is in your icons again. If you have Magisk, you should have root. You can verify root by either programs that check it root or open a terminal window and type in SU and Magisk will pop up a window asking if you want to give the program root access.
Hope that helped.