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
I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
ourangashane said:
I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
Click to expand...
Click to collapse
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
echo92 said:
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
Click to expand...
Click to collapse
That would be my guess as well. I don't get why some are so impatient to get Nougat that they risk flashing firmware not intended for their devices. Then they wonder why they are having issues. Oh well!
pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
No, no update yet.... i just flashed the indian version from the forum..
echo92 said:
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Click to expand...
Click to collapse
Had i just used my eyes lol... Id been looking for a fastboot 93-14, i must have been way too tired lol.. thank you
Solved, Check below for solution
Please help me to revive my Moto G4 .
Hi got a pure evil phone (Hard Bricked)
How This Happened :
Everything was going good then i lost my Volte network, I tried to solve by wiping cache and dalvik cache, didn't worked then wiped data, didn't worked, Then i decided to flash it to stock.
I was in the latest version of Nougat 01 June Security patch a custom kernel with root, TWRP and obviously unlocked bootloader. In first i could not find my version of stock rom which is NPJS25 then i decided to flash another stock which is at November 2016 patch version (NPJ25). When flashing I just left the gpt.bin and bootloader.bin thinking that i already have the latest partition table (Maybe it was an horrible mistake). After flashing i got my VOLTE back everything good now.
Then I searched for system update, got one from December (118MB) installed it, Then searching got another from March(May be) it was getting installed then the disaster happened it got switched off, waited for 5 mins tried to Start it, failing hereafter connected it to Pc, got QSHUSB_BULK in device manager. Then updating the driver and flashing the blankflash i got fastboot(the first sign of live). after that i am not moving.
what i tried
Upon starting it i get "Failed to initialize partition table" in Bootloader logs
When i try to flash gpt.bin from NPJ25 it says "Preflash Verification failed".
Now what i got is a nice fastboot mode, locked bootloader, ****ed up gpt.bin.
Any idea of solving it ??
This Thread Solved my problem, try it if you have same type of problem
You may wish to consult the following blankflash guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 This has links to a blankflash, and GPT/bootloader and a fastboot ROM of the June 2017 NPJS25.93-14-8 stock ROM (that's been around for a little while too). Hopefully that'll rescue your device. Sounds like you need the fastboot June 2017 stock ROM to reflash your GPT, bootloader and core firmware. How did you manage to re-lock your bootloader btw?? (NOTE - the NPJS25.93-14-8 ROM appears to be for retail non-USA devices).
Also, with losing VoLTE, did you confirm with your mobile network operator if it was you or if they were having an outage in your area?
As an aside to anyone else, downgrading from June 2017 with an older stock ROM and then attempting to take an OTA has a very high risk of hard bricking.
echo92 said:
You may wish to consult the following blankflash guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 This has links to a blankflash, and GPT/bootloader and a fastboot ROM of the June 2017 NPJS25.93-14-8 stock ROM (that's been around for a little while too). Hopefully that'll rescue your device. Sounds like you need the fastboot June 2017 stock ROM to reflash your GPT, bootloader and core firmware. How did you manage to re-lock your bootloader btw?? (NOTE - the NPJS25.93-14-8 ROM appears to be for retail non-USA devices).
Also, with losing VoLTE, did you confirm with your mobile network operator if it was you or if they were having an outage in your area?
As an aside to anyone else, downgrading from June 2017 with an older stock ROM and then attempting to take an OTA has a very high risk of hard bricking.
Click to expand...
Click to collapse
Yes that fantastic thread save my phone. What i was doing is that flashing the gpt partition taken out from november Nougat rom and i was getting error because i already had the latest corrupted partition. ''fastboot oem lock'' reports that The devices is not in unlocked form, but that was not actually it. May be the fastboot had trouble getting out the information of state of lock because of corrupted partition but after flashing the latest gpt.bin and rebooting fixed all the problems everything is good as it was. I didn't had to even flash anything after that and phone was also updated to the version it corrupted in.
So the experience told that while updating through OTA it tries to update the partition at last even it had not to. Maybe it is technically not possible check the state, i dont know.
xCALIFIER said:
Yes that fantastic thread save my phone. What i was doing is that flashing the gpt partition taken out from november Nougat rom and i was getting error because i already had the latest corrupted partition. ''fastboot oem lock'' reports that The devices is not in unlocked form, but that was not actually it. May be the fastboot had trouble getting out the information of state of lock because of corrupted partition but after flashing the latest gpt.bin and rebooting fixed all the problems everything is good as it was. I didn't had to even flash anything after that and phone was also updated to the version it corrupted in.
So the experience told that while updating through OTA it tries to update the partition at last even it had not to. Maybe it is technically not possible check the state, i dont know.
Click to expand...
Click to collapse
Good to hear that the guide and just repairing your bootloader/GPT was enough to get your device running.
As I understand it, OTAs check your system version and whether you have a stock recovery/stock kernel and unmodified system, but not necessarily whether your bootloader or GPT are at the same patch level as your system. Thus, the OTA you downloaded thought your device was on the December 2016 patch level, and attempted to patch up to March 2017, but your bootloader was actually from June 2017, so corrupting your bootloader. Hence why taking OTAs are so dangerous after a downgrade, especially recently with the June 2017 update, where Motorola patched a bootloader vulnerability, and thus may prevent you downgrading to stop you from re-opening the vulnerability.
Incidentally, this OTA behaviour isn't isolated to our Moto G4/Plus, we've seen it on Moto X (https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147), Moto Z/Play and other Moto devices, and I've noted it on LG devices too. It's just becoming riskier to update via OTA if you've downgraded. The safest way is either to not downgrade or update using the latest fastboot ROM (preferably the same build as the one you had previously)
echo92 said:
Good to hear that the guide and just repairing your bootloader/GPT was enough to get your device running.
As I understand it, OTAs check your system version and whether you have a stock recovery/stock kernel and unmodified system, but not necessarily whether your bootloader or GPT are at the same patch level as your system. Thus, the OTA you downloaded thought your device was on the December 2016 patch level, and attempted to patch up to March 2017, but your bootloader was actually from June 2017, so corrupting your bootloader. Hence why taking OTAs are so dangerous after a downgrade, especially recently with the June 2017 update, where Motorola patched a bootloader vulnerability, and thus may prevent you downgrading to stop you from re-opening the vulnerability.
Incidentally, this OTA behaviour isn't isolated to our Moto G4/Plus, we've seen it on Moto X (https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147), Moto Z/Play and other Moto devices, and I've noted it on LG devices too. It's just becoming riskier to update via OTA if you've downgraded. The safest way is either to not downgrade or update using the latest fastboot ROM (preferably the same build as the one you had previously)
Click to expand...
Click to collapse
Yes, exactly. Before upgrading through One should keep in mind that if the update was built for him or not in context of modification to his device.
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
xdafan15 said:
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
Click to expand...
Click to collapse
All of these questions are answered in the threads you referenced...
1) Yup, that's fine.
2) Same, remember to extract it... Although I would recommend extracting it to a unique directory and add platform-tools to your path
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
4) Yup, good there
5) Sideload in this regard is accomplished through stock recovery, start stock recovery and select "Apply update from ADB" then execute "adb sideload update.zip"
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Thanks for your help, @acejavelin! Some further clarifying questions-
acejavelin said:
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
Click to expand...
Click to collapse
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
acejavelin said:
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
Click to expand...
Click to collapse
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
acejavelin said:
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Click to expand...
Click to collapse
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
[/QUOTE]
xdafan15 said:
Thanks for your help, @acejavelin! Some further clarifying questions-
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
Click to expand...
Click to collapse
Using the 'oem lock' commands will fail, and it will get stuck in fb_mode that you have to clear. Better to just use the fb_mode commands up front.
xdafan15 said:
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
Click to expand...
Click to collapse
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
xdafan15 said:
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
Click to expand...
Click to collapse
You can chose whether to lock the bootloader or not by flashing the Nougat image, the question is which do you want? Just flashing an image won't make your software status "official" in most cases. We have seen some cases where it does, but we don't know why and in most cases it will stay unofficial until you accept an OTA update, then somehow it miraculously becomes official. The key to remember here is once you accept an OTA that is a higher version than the stock images we have, you have no way to lock the bootloader, so if you want to lock your bootloader in your current state the only possible way is to flash the NPH25.200-22 image using the locking commands, because if you don't lock at this point and accept an OTA update you cannot relock the bootloader until (or if) we get a newer factory image.
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick such that a mainboard replacement is necessary to fix it, which Moto won't do because you unlocked the bootloader, so basically the phone is trash.
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
acejavelin said:
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
Click to expand...
Click to collapse
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
acejavelin said:
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick....
Click to expand...
Click to collapse
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
xdafan15 said:
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
Click to expand...
Click to collapse
Yes
No
Yes, except watch the number of sparse chunks
Yes, as long as you flash the full image and not as an OTA.
No
I guess this conversation is going all over the place... are you wanting to return to stock and lock the bootloader or run a custom ROM? You can't really do both. If you want to return to stock, that depends on your current version, if you want to run custom there are less constraints. This is a 2 year old device, just pick one and go with it.
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
xdafan15 said:
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
Click to expand...
Click to collapse
Honestly, the smart bet would be to flash the NPH25.200-22 image, then do NOT take any OTA. Then go ahead and flash TWRP and LineageOS. You can always go back to the full image without issues of "downgrading".
At this time the 25.200-22 image is the newest we have and downgrading can never be perfect. If there is no reason to take the OTA (like you are going to just flash Lineage anyway), then don't take it... At least you have an easy out.
The main reason for this is we don't have an image for 25-201.2 and we don't know when, or even if, we ever will. For example, we never did get an image of Marshmallow 18-16 and at this point I doubt we ever will.
Thanks for the excellent support, @acejavelin! That's why I love XDA.
@acejavelin I was on official (stock) 7.0, build NPH25.200-23. I installed unofficial LOS 14.1 (by Hashbang) because I have the N modem, and official LOS 14.1 only supports the M modem. I later decided to go back to stock. As we all know the NPH25.200-23 factory images have not yet been (or ever will be) released, so I followed your guide on how to revert to stock, except I flashed the available NPH25.200-22 partitions (the ones that flashed, anyway, minus the ones that gave Preflash Validation Error) without relocking the bootloader, and now I am back to NPH25.200-22. I also immediately received the notification for the -23 OTA but I did not install it. My question is this: Can I accept the -23 OTA or will I risk bricking? I never downgraded to M, I only had unofficial LOS 14.1 builds, and now the stock -22 build.
My battery is acting all weird, shutting down at about 70%, plugging it again and showing 50%. When I boot, if I unplug it will immediately shut down. Basically it's plugged in the whole time. I have no idea what's causing this, the fact that I flashed unofficial LOS, or because of a faulty battery since I had changed it before flashing LOS), or because of partitions mismatch. So I'm trying to narrow it down and pinpoint the cause. But it seems that every time I try something, it makes the battery worse.
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
acejavelin said:
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
Click to expand...
Click to collapse
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
discovery94 said:
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
Click to expand...
Click to collapse
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
The issue of the MM vs. N modems is part of the reason I started this thread. My understanding was that official Lineage OS 14.1 would only work properly if the phone was still running MM firmware because LOS 14.1 was not configured to handle the N modem as written above by @discovery94. It seems like the unofficial LOS 14 by @Hashbang173 has some problems, so it seemed safer to stay on MM. But @acejavelin's advice to me was to upgrade to N before switching ROMS which would seem to severely limit choices of ROMs
I guess the options are stay on MM and have a large selection of ROMS (including official LOS 14.1)
or upgrade to N and only select form Hashbang's LOS, RR by LuisG, and AOSP EX by Obsolete1,
or maybe upgrade to N, then extract the modem from MM stock firmware and flash it to avoid the modem mismatch problem.
Have I summed this up properly?
acejavelin said:
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
Click to expand...
Click to collapse
So the OTA was unsuccessful. The recovery first showed installing update, then displayed "Error", and then the phone rebooted and displayed an update not successful screen (Images attached). I guess the only way is to use the factory images, but I won't even get my hopes up for that.
Will i recive OTA update if i unlock the bootloader?
Androidtroll said:
Will i recive OTA update if i unlock the bootloader?
Click to expand...
Click to collapse
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise your phone should still function as if it weren't unlocked.
In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.
bazinga137 said:
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise, your phone should still function as if it weren't unlocked.
Click to expand...
Click to collapse
Yes the Same thing Happened
I had TWRP recovery and I installed the Security Patch
my Phone Stuck at TWRP
but it has One solution
First, take the data backup of all in twrp at your sd card
now install any custom Rom
Reboot your device and check the rom is working or not
do reboot and go back to your Twrp and Restore the backup
I tested it and It worked perfectly
echo92 said:
In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.
Click to expand...
Click to collapse
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom
Androidtroll said:
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom
Click to expand...
Click to collapse
Just unlocking the BL wouldn't be enough to edit system files. You'll need root privileges to do so and for that you will have to flash/boot TWRP to install a root app like magisk.
So all the useful information @echo92 posted above is significant for you.
Sent from my Moto G5 Plus using XDA Labs
Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.
Frawgg said:
Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.
Click to expand...
Click to collapse
If anything in /system or /oem is tampered like installing a camera mod (or just mounting system r/w) the only way to receive future OTA updates is flashing your current ROM incl. stock recovery via fastboot.
Sent from my Moto G5 Plus using XDA Labs