Does anyone have and/or able to post the most recent factory images for the XT1575? Given my phone previously received an OTA update to NPH25.200-23 (November 2017), I cannot use the NPH25.200-22 images posted here to flash my phone (or lock the bootloader). My understanding is that is not possible to downgrade to the Android 6.0 firmware after this OTA update or to a lower build number either.
I believe a large number of users should have received the OTA to NPH25.200-23, if anyone has the stock image for this build I would really appreciate it. As of now I am unable to restore my phone or lock my bootloader, flashing to NPH25_200-22 fails. Really appreciate any help, sure regret accepting the OTA update to NPH25.200-23. I received a warranty replacement from Motorola that was still running Marshmallow, and as soon as I fired it up it presented the OTA update to NPH25.200-23 (not NPH25.200-22), and shortly thereafter a security patch to October 2017. At this point I decided to unlock the bootloader and play with customer roms which was bad move, as none of the custom roms support the Nougat firmware on the XT1575, and all the ones I tried loaded would result in a boot loop. I couldn't find any mention of this constraint on the LineageOS or AICP websites, if only I had known!
Pretty sure my only options are to flash a factory image of build NPH25.200-23 or wait for the custom roms to support the more recent firmware. Any other suggestion would be appreciated. Really hoping someone has the NPH25.200-23 factory image.
You can't relock BL(maybe in future).
But
You can flash(Asia, LA, US, dd EU) any stock Nougat and ota's will be installed succesfully.
What fails when you flash .22? gpt.bin .. bootloader... a sparsechunk? BTW good luck getting the .23. Was surprised to even get the .22 firmware.
BL, GPT always fail if lower version.
dzidexx said:
BL, GPT always fail if lower version.
Click to expand...
Click to collapse
Not true. Downgraded from nougat .201.1 to .22 only thing failed was gpt.bin. So if that was the only thing that failed when he did the .22 flash from .23 then replace the gpt.bin. But if also the bootloader then hes screwed till firmware is available.
Related
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
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
Hello everyone, I stumbled upon this problem but I can't find much useful information to solve this: I rooted my Moto G4 Plus and after some time I decided to unroot and I flashed stock rom in it with unlocked bootloader. After that I'm stuck at Marshmallow and can't receive Nougat update. Everything was fine before I rooted and flashed stock rom in it with unlocked bootloader but now it doesn't seem to update. My model number is XT1642. How can I solve this problem and receive OTA updates? I also want to relock my bootloader. So to sum it all up: I want my device to be just as after I bought so to speak.
Depending on what Marshmallow ROM you flashed, it might have not been the correct version for your software channel, and thus your device won't have received an OTA (since the server is expecting a different build to the one you have).
If you wish to update to Nougat and re-lock your bootloader, you may wish to flash the June 2017 fastboot ROM, which should also re-lock your bootloader if you use the commands mentioned. Be aware that re-locking your device may wipe your data, back up and keep your data off your device until you're done.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for the June fastboot ROM. If at a later date you choose to unlock your bootloader again, do not downgrade your device to an older stock ROM from the June update.
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.
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