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.
Related
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.
Hi everyone When I am Rooted My Moto G4 Plus and install custom rom thn i downgrade to Official 7.0 with Dec 2016 Security Patch Update and when i try to Official OTA update of march 2017 with unlock bootloader but my phone goes hardbrick than via "blank flash" now i am on Official stock June 2017 security patch update and i Relocked my bootloader.....So My Question Is can i Update Further Upcoming Security patch or any official OTA update..??? Or My phone get Hardbrick????? Plz reply....
pritesh barot said:
Hi everyone When I am Rooted My Moto G4 Plus and install custom rom thn i downgrade to Official 7.0 with Dec 2016 Security Patch Update and when i try to Official OTA update of march 2017 with unlock bootloader but my phone goes hardbrick than via "blank flash" now i am on Official stock June 2017 security patch update and i Relocked my bootloader.....So My Question Is can i Update Further Upcoming Security patch or any official OTA update..??? Or My phone get Hardbrick????? Plz reply....
Click to expand...
Click to collapse
I have same question ,but I'm asking you can I unlock bootloader again
1) You can unlock the bootloader again, each time will wipe your device however. I think you can use the same unlock code as issued by Motorola (provided nothing has changed with your device hardware - i.e. you have the same motherboard).
2)As I mentioned in the other thread, if you've hard bricked and you flashed the June 2017 stock ROM in its entirety - all commands and wipes, then you may be okay to accept and install OTA updates. This is dependent on you having flashed all parts of that stock ROM, so your device is at the same patch level - if you have not, then taking the OTA might hardbrick you again. The OTA updates do not necessarily include complete files, they mainly are a collection of patches, and assume your device is at the same patch level (GPT, bootloader, system, kernel, and other firmware are all at the June 2017 patch level, for example).
If you're worried at all about the OTA updates, wait for an updated fastboot stock ROM with the included update, which is safer.
3)Once you've taken any OTA updates newer than June 2017, it is no longer safe to attempt to flash the June 2017 stock ROM - if you want to go back to stock, wait for an updated stock ROM to be leaked. Else, you could downgrade (which I do not recommend), but do not accept OTA updates. Our newest blankflash works on B1:06 bootloaders, I do not know if it works on newer bootloaders. If not, and you hard brick, you'll likely have to wait for a new blankflash or pay for a new motherboard. A new motherboard is around 7000-10000 rupees or your regional equivalent, from what I've seen.
echo92 said:
1) You can unlock the bootloader again, each time will wipe your device however. I think you can use the same unlock code as issued by Motorola (provided nothing has changed with your device hardware - i.e. you have the same motherboard).
2)As I mentioned in the other thread, if you've hard bricked and you flashed the June 2017 stock ROM in its entirety - all commands and wipes, then you may be okay to accept and install OTA updates. This is dependent on you having flashed all parts of that stock ROM, so your device is at the same patch level - if you have not, then taking the OTA might hardbrick you again. The OTA updates do not necessarily include complete files, they mainly are a collection of patches, and assume your device is at the same patch level (GPT, bootloader, system, kernel, and other firmware are all at the June 2017 patch level, for example).
If you're worried at all about the OTA updates, wait for an updated fastboot stock ROM with the included update, which is safer.
3)Once you've taken any OTA updates newer than June 2017, it is no longer safe to attempt to flash the June 2017 stock ROM - if you want to go back to stock, wait for an updated stock ROM to be leaked. Else, you could downgrade (which I do not recommend), but do not accept OTA updates. Our newest blankflash works on B1:06 bootloaders, I do not know if it works on newer bootloaders. If not, and you hard brick, you'll likely have to wait for a new blankflash or pay for a new motherboard. A new motherboard is around 7000-10000 rupees or your regional equivalent, from what I've seen.
Click to expand...
Click to collapse
Now I Hve Successfully Relock My Bootloader and now i am on stock June 2017 Can I Reflash With Same June 2017 without Unlocking Bootloader Again because during Relock i used Command Directly From X Da Thread For Relock Bootloader and Don't Sure Fully Install June 2017 Rom So Want To Reflash With 'Stock Flash.Bat' File So I Will Get OTA Without Waiting For Updated Fastboot Stock Rom....So Can I Flash June 2017 Without Unlocking Bootloader....??? Plz Reply...
pritesh barot said:
Now I Hve Successfully Relock My Bootloader and now i am on stock June 2017 Can I Reflash With Same June 2017 without Unlocking Bootloader Again because during Relock i used Command Directly From X Da Thread For Relock Bootloader and Don't Sure Fully Install June 2017 Rom So Want To Reflash With 'Stock Flash.Bat' File So I Will Get OTA Without Waiting For Updated Fastboot Stock Rom....So Can I Flash June 2017 Without Unlocking Bootloader....??? Plz Reply...
Click to expand...
Click to collapse
Can I Reflash With Same June 2017 without Unlocking Bootloader - yes, the stock ROMs we have access to should be signed by Motorola, so should flash on a locked or unlocked bootloader regardless.
You should be able to get OTA updates without waiting for an updated stock ROM. From your previous posts, you seem unsure of this. It is still up to you and your responsibility whether you choose to take an OTA or wait for the updated stock ROM. If you re-locked your bootloader, then you must have been able to re-flash the entire stock ROM, else you may have failed to boot (as you'd have likely failed the verification checks performed by a locked bootloader). Thus, your device might be okay to update. Again, as I have mentioned previously in replies to your posts, if you are worried about hard bricking, then wait for the updated fastboot ROM. The updated fastboot ROM has complete files and thus has a lower risk of damaging/bricking your device. I understand you're eager to get the latest OTA updates, however you could wait and see if there are any bugs/outstanding issues before updating.
Depending on the commands in that stock flash.bat file, you may wipe your device, so back up accordingly.
As an aside, how are you not sure you flashed the full stock ROM? Surely if you followed the guide and used all the commands, you'd have fully flashed? If you look in the stock flash.bat script (open it in Notepad or a text viewer), you'll note the commands should be the same as what you used previously?
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.
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
So, we all know Motorola will eventually (aka never) release Oreo for the G5 Plus.
I am way too anxious so I am going to flash a Custom ROM until they deliver it. However I am quite afraid about something.
I plan to use Lineage 15.1 until Oreo comes out for the G5 Plus. However, I am kind of afraid that I may screw things up when the OTA comes out.
I have recently hard bricked my Moto G 2014 because of OTAs and Bootloader.
So, Oreo releases...
Will it be fine to install the OTA (through normal System Update check) having the latest Stock ROM Firmware for my region installed? (I would erase Lineage 15 and use fastboot to flash Stock again)
Or will I instead need to wait for someone to post the system images and flash it through fastboot instead? (I assume I would need to install the OTA through normal methods because of bootloader changes but still...)
I just don't want this: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-t3694119
To happen.
You won't get system updates when you are on a custom ROM like Lineage OS or any other custom ROM. The only system updates you might get are ROM updates if the ROM maintainer has that feature built in.
If official Oreo comes out and you are on the correct stock firmware for your model and region, everything should work fine.
Before flashing custom roms you should backup your efs partition using twrp else you could lose your imei(recoverable) / volte(not recoverable till now) when flashing fastboot firmwire.
You need to flash fastboot firmwire to receive oreo ota.
If you want to avoid hard bricking, then you must flash the same stock ROM or newer onto your device when you revert back to stock firmware.
I imagine your Moto G 2014 got bricked when you took an OTA update? That could have occurred if firmware older than what was present on your device was flashed (bootloaders cannot be downgraded), and like in that thread you linked, attempting to use OTA updates would corrupt your newer bootloader with the older OTA patches, leading to a hard brick.
As mentioned above, if you revert to the correct build for your region and matching your current build at least, you should be okay to receive OTA updates (should also include up to Oreo). Alternatively, you could wait for the Oreo fastboot ROM to be safe, or the Oreo TWRP flashable for a near stock ROM experience (since TWRP flashables shouldn't care about your bootloader or GPT partitions, do it'd be difficult to brick your device. However, TWRP flashable stock ROMs aren't OTA compatible).
Before you unlock your bootloader and flash TWRP/custom ROMs, make a note of your current build version and see if you can find a stock ROM leaked of that build, so you can be sure that you're reverting to the right build for your device.
Just do not flash older stock Motorola firmware to your device or if you do, do not use OTA updates.
Yeah, I did some research and now I understand what happened. Thanks for the comments.