Related
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.
Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands
Hi guys,
It may be a silly Question for this Device , let me tell you my device specs :
Device : G4 Plus XT1643(India)
Rom : Stock (Soak NPJ75.25.2)
NON-Root and Locked Bootloader
What does the OTA.zip checks for ?
Boot image version (may b bootloader version) or recovery version ?
If its all about bootloader, then it needs to b unlocked voiding warranty.
But If its about Recovery..........Changing the Recovery to older version might help updating from Old Soak to New Official Build.
So, Did any one try flashing an older recovery thru fastboot on locked bootloader ? or Can we if its possible ?
ex: Replacing 7.0 recovery with last 6.0 build recovery. I do this for my ZenFone 5 just to avoid updating from very old builds.
Is this possible on G4 Plus ? without warranty Void issues....if possible.
p.s: NPJ93-11 gives Status 7 error on NPJ.75-2.
I tried to flash old recovery but it fails due to higher bootloader version.
Same question. Experts please advise and find a solution to get official update without unlocking the bootloader.
praveenbda said:
Same question. Experts please advise and find a solution to get official update without unlocking the bootloader.
Click to expand...
Click to collapse
You don't need to unlock your bootloader to get an OTA. Its only to let you mess with your recovery and enable flashing henceforth.
However, you'll need to unlock your bootloader to flash/boot a custom recovery and subsequently flash a ROM.
But if you want an OTA, your system (including bootloader, recovery, system, etc) needs to be untouched.
If you've already upgraded to a soak test, remember - you would've overwritten your MM bootloader and recovery with an N version one (from the Soak you sideloaded)
Again, all major official updates (except small incremental one like patches maybe) look for a previous version of the OS (in our case - Stock MM)
And yes, as long you're on MM and not upgraded to N soak ever, once you unlock your BL, you can relock it using methods stated in the guide thread. Just that it voids your warranty (as the request code is generated by Lenovo/Moto, essentially letting you unlock) But if you've flashed the N Soak - you can't downgrade your bootloader just yet ( you'll get a Preflash Validation error)
Because a system update looks the stock, untouched firmware (Stock MM)
That's why you won't be able to sideload the Official N update if you're already on a soak test update - because it doesn't have the MM bootloader and recovery etc files it's looking for.
Sent from my Moto G4 Plus using Tapatalk
Hi!
I have got two G4, one with Marshmallow and one with Nougat.
The one on N (offical N, updated by OTA and did a full wipe) has lots of problems with BT, and I want to downgrade it to MM.
I have read lots of posts, here and everywhere else, and saw some vids about the procedure. But I still have some doubts about the proccess:
* Most of the procedures I have read relate to downgrade from N leak to MM in order to upgrade to official N. I have seen someone ask if the same procedure could be used to downgrade from offical N, but no answer. Can I use the same procedure to downgrade from official N?
* Some say you have to unlock the bootloader, others make no mention of it. Some say you should not write gpt.bin and bootloader from the MM ROM as N udated them and it is not possible to downgrade them. Do I have to unlock the bootloader before using fastboot to write the MM ROM? Should I avoid writing gpt.bin and bootloader?
I don't mind voiding the phone warranty, and I don't mind not being able to OTA update future versions.
Thank you very much.
Regards.
If you have bootloader locked, you can't overwritte nothing including system, boot, bootloader and gpt. I tried with my Moto G4 and i can't go back from official N to official MM through fastboot
Thank you.
So I understand I have to unlock the bootloader.
Now I just need to make sure if I should overwrite gpt and bootloader with MM versions (coming from stock N) or not.
Regards.
CalvinH said:
Thank you.
So I understand I have to unlock the bootloader.
Now I just need to make sure if I should overwrite gpt and bootloader with MM versions (coming from stock N) or not.
Regards.
Click to expand...
Click to collapse
A couple of weeks ago, I read something about it. I think you should not overwrite the bootloader and recovery but I do not remember very well.
But if you have your bootloader unlocked just flash (or boot into) a custom recovery and make a backup of everything and after play along a while
lerg96 said:
A couple of weeks ago, I read something about it. I think you should not overwrite the bootloader and recovery but I do not remember very well.
But if you have your bootloader unlocked just flash (or boot into) a custom recovery and make a backup of everything and after play along a while
Click to expand...
Click to collapse
Thank you.
Based on the overwhelming popularity of this thread (thanks lerg96!) I have decided to come back and tell how it went.
I had a Moto G4 with official Nougat. I wanted to downgrade it to MM.
The first problem is that I didn't find the .63 ROM (last MM one) for my device (XT1622). I found the 23.5 version (previous one), and the .63 version for the XT1624. Since 22 and 24 differ on LTE bands and so, I decided to use the older but right ROM.
First attempt: downgrade without unlocking bootloader... NO WAY.
Second attempt: unlock bootloader + downgrade without overwriting bootloader and gpt.bin. :good::good:
I got the boot warning message, but everything went ok and my BT problems are gone. I got the .63 OTA notification, but didn't installed it as I read scary histories about doing it.
Regards!
now that your bootloader is unlocked, install TWRP and make a backup of your system. I used TWRP to restore my OS. I went from Nougat back to MM, I am sure you can go the other way around too.
also, the fastboot method for reload the os seems to work well on phones with unlocked bootloaders.
Hello, as the title says, I am a confused semi-noob with a rooted USA G5+. I wish to apply all the security updates to my phone (and upgrade to Oreo when it is available). I've read many, MANY guides to updating the G5+ and have some questions both general and specific. I'm using a USA Moto G5+ purchased the first week it was available in USA in March, rooted using a guide from this forum (which I can no longer find). I'm a mostly-noob. I can follow guides, but I am at "beginner-intermediate" familiarity with *nix systems, terminal commands, etc - for example I know that if you need superuser permissions to rm -rf something, you should be VERY sure that you want to delete that thing (and that you should back said file/directory up before doing anything!).
First, here's my system info:
Android version: 7.0
Model: XT1687
Software channel: retus
Build number: NPN25.137-33
Android security patch level: 1 January 2017 eek
Baseband version: M8953_02.03.07.06R POTTER_NA_CUST
Rooted using Magisk 11.6, SuperSU, and TWRP installed (need to check version, will update with this ASAP after I get off this telecon I'm currently on).
The PC I am using to root my phone is running Ubuntu 14.04 - I think this is relevant because a lot of easy GUI phone tools are Windows-only.
My questions are as follows:
1) There are a number of update guides for the G5+, some of which involve unrooting and locking the bootloader then running OTA updates, and some involve directly flashing ROMs to the phone. Which method is better? Which is easier? Which method is most difficult to brick my phone?
2) Which ROM do I want? My current build number is NPN25, but the system update prompt is for NPNS25.137-33-5. Shouldn't the NPNS only appear for G5S phones, not my basic usa G5+ ?
3) I'm on RETUS software channel - many guides are for RETEU and RETIN (EU and India). Besides the ROM used, can I just follow those guides to the letter (again, using the correct USA ROM) with my phone?
Thanks in advance for your help.
1.) It depends on what you want. If you want a stock experience, then unlocking the bootloader and rooting is what you want. Otherwise flashing a custom rom should do the trick. Neither should cause you to brick your phone. Just back up your boot partition and you should avoid any bootloops. Do not ever, ever flash the bootloader. Both are easy to do imo.
2.) You said you rooted your phone already. Did you happen to flash an entire stock rom to your phone? Maybe you downloaded the wrong one. I am on NPN25.137-83 and have the same phone (XT1687)
3.) All you need to do to root this phone is to unlock the bootloader through Motorola (which you should have already done if you are rooted), boot into bootloader (adb reboot bootloader), then boot into recovery (fastboot boot twrp.img). I kept my /system partition untouched so I flashed Magisk-v14.zip from an SD card that I inserted. That's pretty much it.
I also recommend flashing ElementalX kernel afterward, but that's not 100% necessary.
dunderball said:
1.) It depends on what you want. If you want a stock experience, then unlocking the bootloader and rooting is what you want. Otherwise flashing a custom rom should do the trick. Neither should cause you to brick your phone. Just back up your boot partition and you should avoid any bootloops. Do not ever, ever flash the bootloader. Both are easy to do imo.
2.) You said you rooted your phone already. Did you happen to flash an entire stock rom to your phone? Maybe you downloaded the wrong one. I am on NPN25.137-83 and have the same phone (XT1687)
3.) All you need to do to root this phone is to unlock the bootloader through Motorola (which you should have already done if you are rooted), boot into bootloader (adb reboot bootloader), then boot into recovery (fastboot boot twrp.img). I kept my /system partition untouched so I flashed Magisk-v14.zip from an SD card that I inserted. That's pretty much it.
I also recommend flashing ElementalX kernel afterward, but that's not 100% necessary.
Click to expand...
Click to collapse
Thanks for your reply. I am already rooted (from a guide on this very forum, which appears to have been deleted as I can no longer find it), and flashed a stock rom - the only one available in late March 2017, which was NPN25.137-33. XDA has MANY links to stock ROM images for the G5+, but none say which region the ROM is for (does it matter? There are SOME hardware difference between regions, no?). How do I know which Potter ROM is for my USA hardware?
I don't need a guide to root (as I'm already rooted). I need a guide to flashing updates, of which there are many. Hence my question of whether I should lock bootloader + return to stock and take the OTA directly from the phone, or sideload updated stock ROMs one by one. I'm interested in as close a stock experience as possible, so no custom ROMs.
I also don't know whether I modified the /system partition during my original hasty rooting - any way to check that?
boogiebot said:
Hello, as the title says, I am a confused semi-noob with a rooted USA G5+. I wish to apply all the security updates to my phone (and upgrade to Oreo when it is available). I've read many, MANY guides to updating the G5+ and have some questions both general and specific. I'm using a USA Moto G5+ purchased the first week it was available in USA in March, rooted using a guide from this forum (which I can no longer find). I'm a mostly-noob. I can follow guides, but I am at "beginner-intermediate" familiarity with *nix systems, terminal commands, etc - for example I know that if you need superuser permissions to rm -rf something, you should be VERY sure that you want to delete that thing (and that you should back said file/directory up before doing anything!).
First, here's my system info:
Android version: 7.0
Model: XT1687
Software channel: retus
Build number: NPN25.137-33
Android security patch level: 1 January 2017 eek
Baseband version: M8953_02.03.07.06R POTTER_NA_CUST
My questions are as follows:
1) There are a number of update guides for the G5+, some of which involve unrooting and locking the bootloader then running OTA updates, and some involve directly flashing ROMs to the phone. Which method is better? Which is easier? Which method is most difficult to brick my phone?
2) Which ROM do I want? My current build number is NPN25, but the system update prompt is for NPNS25.137-33-5. Shouldn't the NPNS only appear for G5S phones, not my basic usa G5+ ?
3) I'm on RETUS software channel - many guides are for RETEU and RETIN (EU and India). Besides the ROM used, can I just follow those guides to the letter (again, using the correct USA ROM) with my phone?
Thanks in advance for your help.
Click to expand...
Click to collapse
I don't own a G5 Plus, so up to you how much you take on board (I have a G4 Plus) - as always, please double-check anything you're not sure of. Stock ROM firmware is not to be trifled with...
1)Either way, to use OTA updates on the stock Motorola ROM, you'd have to re-flash back to stock (full stock, not TWRP flashables). You do not have to re-lock the bootloader, OTA updates can install with an unlocked bootloader. The key rule appears to be at least un-modified (read-only) stock system, stock OEM, stock recovery, stock logo and stock boot.img (kernel) partitions that are from all the same stock patch level and match the patch level of your bootloader (mixing and matching patch levels, e.g. older stock firmware with a newer bootloader is a really bad, brick causing, idea...). If you swiped to let TWRP make modifications, then you'll likely have modified the /system partition and require re-flashing/restoring an unmodified /system partition. Easiest way to restore these all to stock would be a firmware flash.
a)Leaving your bootloader unlocked allows you to root your device later, plus easier for troubleshooting. Only requires re-flashing stock firmware (which can leave your data intact, though back up as always).
b)Re-locking your bootloader is more complex, plus involves erasing your data. Cleaner, but does not restore your warranty. However, depending on your service centre and US consumer laws, service centres may take your device in for repairs depending on the fault.
c)Either path would require you to re-flash the same/newer stock ROM onto your device to successfully accept and install OTA updates. As you're on the Jan 2017 NPN25.137-33 update, that is the original update for US/EU devices (though as soon as you update, you cannot roll back to this build without potential issues). If you're worried about hard bricking, then re-locking will force you to only accept updates. Downgrading your stock firmware is only risky if you take OTA updates, so either re-lock your bootloader or do not downgrade your device stock firmware. That means only flashing NPN25.137-33 or later firmware, and then staying in step with your device firmware as you update. Staying in lock step can be difficult due to the sparsity of certain stock ROMs (Motorola is not keen on releasing stock ROMs, so generally it's been up to us to 'acquire' said stock ROMs.) Hence, be careful what you flash.
d)Either method would remove root, TWRP and magisk, though you could re-apply them once you've updated.
2)NPNS.... updates are for G5 Plus devices, the S denoting a security update (though Motorola's update naming system is a little inconsistent). G5S Plus devices appear to be running updates starting with NPS, G5 and G5S are NPP.
NPNS25.137-33-5 should be the next update in line for you, depending on your network (other devices on other networks do appear to get different updates, especially Verizon). The OTA servers should be suggesting the correct OTA build anyway!
3)Should be able to use the guides, just ensure you use the correct stock ROM. If you're on NPN25.137-33, here's a link for the stock ROM of the same build: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Also, you may wish to look into using this stock ROM (NPNS25.137-33-5, May 2017 security patch, should be the same as the update you're prompted to receive) to update and return to stock in one go: https://androidfilehost.com/?fid=961840155545594421
Either way, if you just want to revert back to stock, and wish to keep your data, then do not re-lock your bootloader and omit any fastboot commands with erase userdata (erase cache is okay) - such as the following fastboot commands you can try. Of course, back up your data as always just in case. Ensure also that you flash the same build as what is currently on your device - other builds may work, but render OTA updates inoperable unless you revert to the intended build for your region (but this process may damage your device and Motorola may ask you to pay for any damage caused in this regard).
Please verify these before using, check the number of sparse chunks matches the number in the stock ROM, and that these commands will not re-lock your bootloader. If you get pre-flash validation errors or security downgrade errors, double check what stock ROM you have present on your device and what stock ROM you're flashing, as these errors appear if trying to flash an older stock ROM (which as I've mentioned above is NOT recommended):
Code:
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot oem fb_mode_clear
fastboot reboot
Good luck whatever you decide.
Hello!
I've the Indian variant of the Moto G5 Plus (XT1686), software channel: Retin. I have unlocked the device and flashed a custom ROM. I want to return to stock now but I have a few questions.
1) Where can I get the latest factory image for my XT1686?
2) Which one should I flash on my device amongst AMZ, RETLA & RETAIL?
3) I was on the November security patch before I unlocked and rooted. Should I flash stock, will my device continue receiving ota updates that are released for India?
4) If I flash the firmware that you guys will link me to here, will it hard brick my device when I try for ota update in the future? I read somewhere about mismatch in the partition table will lead to 9008/ some error and device won't go in bootloader mode and that you'll need blankfiles to revive your device and stuff.
Please tell me what to do to return to my complete stock image and to continue receiving ota updates safely on my XT1686, RETIN Software Channel?
1) To the best of my knowledge, this NPN25.137-92, Nov 2017 stock Motorola firmware, is the latest for retIN (retail India) devices, amongst other regions. https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-patch-november-npn25-137-92-t3718976 It's been received by OTA to users, indicating it's been formally deployed in India and other regions too. Please verify this before flashing
Flash using the flashing instructions provided in this post: https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but using the above NPN25.137-92 ROM - the flashing instructions should apply to this ROM.
2)As you're on retail India, you want retail stock ROMs. AMZ are only for Amazon Prime devices (bootloader locked to Amazon, adverts on the lockscreen) and whilst you could flash retla (retail Latin America), it may cause problems for your device later down the line.
3)Provided you flash the correct stock firmware for your region, you should continue to receive OTA updates.
4)As this should be the same firmware as you had previously, you should not hard brick when receiving OTA updates in the future. Users appeared to commonly hard brick when they attempted to flash stock Motorola firmware older than the stock firmware they had (custom ROMs don't appear to matter here), then attempted to use OTA updates. You cannot downgrade bootloaders, thus you have a mismatched bootloader and system - your new bootloader and your downgraded system - so using an OTA update would flash older bootloader files. As OTA updates do not have the same checks as fastboot for bootloaders, that would corrupt your newer bootloader and hard brick your device. The OTA updates don't appear designed to consider downgraded devices, i.e. newer bootloaders but older stock systems, hence why Motorola likely warns you that whatever happens when unlocking the bootloader is the user's responsibility. If you were in that situation, then flashing fastboot ROMs would be the safest way to update.
However, as you're being conscientious enough to flash the same or latest firmware, then this should not occur. To summarise, hard bricks only appear to occur when downgrading/cross flashing stock firmware and then taking OTA updates when you previously had newer/different stock firmware on your device.
If you want to be truly sure this is the right firmware to revert back to stock to, then I would like to see your getvar info before proceeding:
1)Boot your device to the bootloader, connect to your computer via USB.
2)In the ADB terminal, type 'fastboot getvar all' without quotes and press Enter.
3)Copy the output to a post here. This output contains device variables including what the last stock firmware was on your device, which will be helpful in verifying the correct firmware for you. You may wish to remove IMEI from the output before posting.
Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is their a way i get info or download link for the stock kernel, please reply. Is it possible that i can just flash the kernel.
Stifmeister11 said:
Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is their a way i get info or download link for the stock kernel, please reply. Is it possible that i can just flash the kernel.
Click to expand...
Click to collapse
Answered on your post, please check