Related
Hello Moderators,
My Device Model : XT 1644 64 GB variant
Current Rom: Lineage OS
Bootloader Status: Unlocked
Since the US variant didn't get the nougat update, I decided to unlock my bootloader and switch to a CM based ROM.Though I love it I've been facing a lot of issues in fingerprint sensor and advanced settings
Now I'd like to go back to my stock ROM and I've few doubts
1. If I don't lock my bootloader again after switching to stock ROM will I be still eligible to receive the official updates?
2. This link to stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 says that it's for the Indian version will it work on the US versions?
3. After flashing the stock ROM will it be okay if I follow this thread and update to nougat https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943?
4.Does the soak test have any bugs?
5.If I'm on the soak test and Once the official nougat is available for my device what should I do?
I have a twrp backup of my stock ROM too
Click to expand...
Click to collapse
@rahulsnair @1chrome
Thanks for taking your time to help me out !!! I'd surely love to return the favour someday
Vijay Selvaraju said:
Hello Moderators,
My Device Model : XT 1644 64 GB variant
Current Rom: Lineage OS
Bootloader Status: Unlocked
Since the US variant didn't get the nougat update, I decided to unlock my bootloader and switch to a CM based ROM.Though I love it I've been facing a lot of issues in fingerprint sensor and advanced settings
Now I'd like to go back to my stock ROM and I've few doubts
1. If I don't lock my bootloader again after switching to stock ROM will I be still eligible to receive the official updates?
2. This link to stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 says that it's for the Indian version will it work on the US versions?
3. After flashing the stock ROM will it be okay if I follow this thread and update to nougat https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943?
4.Does the soak test have any bugs?
5.If I'm on the soak test and Once the official nougat is available for my device what should I do?
@rahulsnair @1chrome
Thanks for taking your time to help me out !!! I'd surely love to return the favour someday
Click to expand...
Click to collapse
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
echo92 said:
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
Click to expand...
Click to collapse
Thanks a lot bro @echo92
I actully followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 these steps now I'm running on stock nougat
Just omitted the bootloader unlock part since you told me that I'll be receiving updates even if the bootloader is unlocked
echo92 said:
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
Click to expand...
Click to collapse
Thanks a lot bro @echo92
I actully followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 these steps now I'm running on stock nougat
Just omitted the bootloader unlock part since you told me that I'll be receiving updates even if the bootloader is unlocked
I am trying to re-lock the bootloader, which requires flashing a stock firmware. But it won't allow flashing any older version due to older security patch. Any ideas?
Is the full firmware for the US version with May security update available somewhere?
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
echo92 said:
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
Thanks a lot.
That worked perfect. Flashed NPNS25.137-35-5 on my US unlocked version and it got the May security patch.
suhridkhan said:
Thanks a lot.
That worked perfect. Flashed NPNS25.137-35-5 on my US unlocked version and it got the May security patch.
Click to expand...
Click to collapse
Hi!!! Hey could you please help me with something? Can you tell me which version of bootloader you have right now?
To know that, you have to restart the phone into bootloader mode, and you have to tell me the number after BL: line
You'll see something like:
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:7) <---- THIS IS WHAT I NEED TO KNOW!!! Please!
Or could you take a picture of this screen?
MarckozZ said:
Hi!!! Hey could you please help me with something? Can you tell me which version of bootloader you have right now?
To know that, you have to restart the phone into bootloader mode, and you have to tell me the number after BL: line
You'll see something like:
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:7) <---- THIS IS WHAT I NEED TO KNOW!!! Please!
Or could you take a picture of this screen?
Click to expand...
Click to collapse
I got this.
BL: C0.8A(*) (sha-c90d6a9-dirty, 2017-04-24 13:31:32)
Just curious, what is the use of this information?
suhridkhan said:
I got this.
BL: C0.8A(*) (sha-c90d6a9-dirty, 2017-04-24 13:31:32)
Just curious, what is the use of this information?
Click to expand...
Click to collapse
I totally hardbricked my potter. To revive it, I had to blankflash some files from other Moto phone. Now I have the bootloader from Moto Z Play (which has the version number I gave you as an example).
I asked you the bootloader version to make sure I can flash the new 135.5-5 bootloader and partition table to return my phone back to normal! But since I have software parts from Moto Z Play, I'm afraid it wont accept potter bootloader back again. So, I'll test this later!
echo92 said:
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
Great question. Mine is the US version with -33, so it must not be an EU firmware. I asked the same question a few weeks back and no one can confirm either way. I do wish we had some confirmation so someone doesn't flash the wrong version. Maybe if everyone responded with version info (screenshot?) and location?
long2ski said:
Great question. Mine is the US version with -33, so it must not be an EU firmware. I asked the same question a few weeks back and no one can confirm either way. I do wish we had some confirmation so someone doesn't flash the wrong version. Maybe if everyone responded with version info (screenshot?) and location?
Click to expand...
Click to collapse
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
Code:
ui_print("Source: motorola/potter/potter:7.0/NPN25.137-33/35:user/release-keys");
ui_print("Target: motorola/potter/potter:7.0/NPN25.137-35/37:user/release-keys");
3)Seems that devices running on other networks are on the 137-33 firmware (e.g. AT&T, retus: https://forums.lenovo.com/t5/Moto-G...ce-G5-plus-stuck-on-NPN25-137-33/td-p/3738547)
4) Seems that there's 2 update paths to the May security patch:
From 137-33 > 137-35 > NPNS25.137-35-5 (this May update seems to be also the wider reported version too for US devices, probably this is the path if you are on the Verizon network)
From 137-33 > NPNS25.137-33-5
I don't know if there's any major differences between the 2 builds besides the VoLTE 911 fix, or if you were on the 137-33-5 build whether you could switch to the Verizon network and be able to make emergency calls on VoLTE (I honestly would hope that fix was rolled into both May patches though...) I'm also not sure what factors decide which update you get, besides possibly being on the Verizon network at some point?
I honestly hope at a later date, Motorola unifies the firmware (like they've done with the G4 Plus), so you can just flash one version rather than multiple different types.
Again, if someone has more information (as I don't have a G5 Plus), feel free to add/correct what I've written!
I have a US version that was shipped with NPN25.137-35 and I'm on the AT&T network.
echo92 said:
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
That last one for indian version?and it's latest .67?
dayask said:
That last one for indian version?and it's latest .67?
Click to expand...
Click to collapse
If you mean the NPN25.137-35 firmware, I don't think it was released in India (unless your device came with it?). As far as I can tell, looks like 137-67 appears to be the latest build currently for India.
echo92 said:
If you mean the NPN25.137-35 firmware, I don't think it was released in India (unless your device came with it?). As far as I can tell, looks like 137-67 appears to be the latest build currently for India.
Click to expand...
Click to collapse
So which one you recommend?
Hello XDA - Am new here, but thought i'd share my info - I have build number NPNS25.137-33-5 (7.0 Nougat) with 1. May (just upgraded from jan/feb if memory serve) as latest security patch. I am from Europe, more specific based in the Benelux area (NL/BE/GE) - If i can provide any more info on the matter, please let me know!
dayask said:
So which one you recommend?
Click to expand...
Click to collapse
I'd suggest staying on NPN25.137-67 if you're on an Indian device, else you may not receive OTA updates. Furthermore, if you swap to 137-35 you may run the risk of bricking your device in future.
So I went ahead and took a chance and flashed the *35 build on top of *33 in rsd lite. It works. Almost immediately I got the OTA of the *35-5 update. I think @echo92 is right and it is more geared towards Verizon. It took me a little to get AT&T to work on LTE here in the US but it all seems fine now.
I had -35 flashed on EU device and no updates for me.
wiceqq said:
I had -35 flashed on EU device and no updates for me.
Click to expand...
Click to collapse
Ah, then you may be on the wrong build for the EU region (I've only seen reports of 137-33 for the EU), and thus the reteu software channel might not have an update for you. I see from your previous post you flashed the 137-35 update onto your device?
I honestly don't know if you can safely revert to NPN25.137-33, but here's a stock NPN25.137-33 ROM to flash via fastboot (as always, back up your data and keep it off your device, as this fastboot ROM will likely wipe your device in the flash): https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I also do not know what will happen if you try to flash the NPNS25.137-35-5 update onto a reteu device (it might work, but could result in you being off the update path still).
Good luck either way.
echo92 said:
Ah, then you may be on the wrong build for the EU region (I've only seen reports of 137-33 for the EU), and thus the reteu software channel might not have an update for you. I see from your previous post you flashed the 137-35 update onto your device?
I honestly don't know if you can safely revert to NPN25.137-33, but here's a stock NPN25.137-33 ROM to flash via fastboot (as always, back up your data and keep it off your device, as this fastboot ROM will likely wipe your device in the flash): https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I also do not know what will happen if you try to flash the NPNS25.137-35-5 update onto a reteu device (it might work, but could result in you being off the update path still).
Good luck either way.
Click to expand...
Click to collapse
Well right now I'm on a custom rom. When I'll decide to revert to stock I'll probably fastboot flash -33 build and see how it goes. Cheers.
echo92 said:
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
Code:
ui_print("Source: motorola/potter/potter:7.0/NPN25.137-33/35:user/release-keys");
ui_print("Target: motorola/potter/potter:7.0/NPN25.137-35/37:user/release-keys");
3)Seems that devices running on other networks are on the 137-33 firmware (e.g. AT&T, retus: https://forums.lenovo.com/t5/Moto-G...ce-G5-plus-stuck-on-NPN25-137-33/td-p/3738547)
4) Seems that there's 2 update paths to the May security patch:
From 137-33 > 137-35 > NPNS25.137-35-5 (this May update seems to be also the wider reported version too for US devices, probably this is the path if you are on the Verizon network)
From 137-33 > NPNS25.137-33-5
I don't know if there's any major differences between the 2 builds besides the VoLTE 911 fix, or if you were on the 137-33-5 build whether you could switch to the Verizon network and be able to make emergency calls on VoLTE (I honestly would hope that fix was rolled into both May patches though...) I'm also not sure what factors decide which update you get, besides possibly being on the Verizon network at some point?
I honestly hope at a later date, Motorola unifies the firmware (like they've done with the G4 Plus), so you can just flash one version rather than multiple different types.
Again, if someone has more information (as I don't have a G5 Plus), feel free to add/correct what I've written!
Click to expand...
Click to collapse
i also am in the U.S. on straight talk with ATT but i have NPN25.137-33 on mine and i got it in july bought it off amazon without ads 64gb version for $299 and its asking me to update to the NPNS25.137-35-5 i believe i soft bricked mine when i updated it now it goes straight to twrp recovery when booting up i used a back up copy i had the phone works fine but still goes to recovery when i shut it down how do i fix this any help will be greatly appreciated.
shaker3000 said:
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
i also am in the U.S. on straight talk with ATT but i have NPN25.137-33 on mine and i got it in july bought it off amazon without ads 64gb version for $299 and its asking me to update to the NPNS25.137-35-5 i believe i soft bricked mine when i updated it now it goes straight to twrp recovery when booting up i used a back up copy i had the phone works fine but still goes to recovery when i shut it down how do i fix this any help will be greatly appreciated.
Click to expand...
Click to collapse
Update TWRP to the latest.
Everyone is crazy about Oreo update!
Today Motorola released new soak test for Oreo with February security patches and I manage to capture it
Here's a GDrive Download Link https://drive.google.com/open?id=1uEIRV1sKq0RGQTQkSWDfgoz-IAqpUL3b
It includes new Moto launcher (Finally replaced Google now launcher), new icons for apps, notification dots, new clock widget, bug fixes, stability improvement and camera improvement
Here are full release notes https://mobilesupport.lenovo.com/us/en/solution/MS126755
Thank you
How do you know it's another soak test and not the final release?
Sent from my XT1635-02 using Tapatalk
razorsbk said:
How do you know it's another soak test and not the final release?
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
If it was official you'd have known that
razorsbk said:
How do you know it's another soak test and not the final release?
Click to expand...
Click to collapse
Because it may have bugs and also night light isn't enabled yet!
From the updater script, looks like you'll need OPN27.74/28 to flash this soak test OTA, and will bring your device up to OPN27.76-12-2/4
Code:
Package expects build thumbprint of 8.0.0/OPN27.76-12-2/4:user/release-keys or 8.0.0/OPN27.74/28:user/release-keys
Having a quick look through the updater script, looks like it'll check and update your boot (kernel), modem, OEM, system and GPT/bootloader partitions. I see references to Google Widevine in the modem images too. At least the error messages seem to be a little more helpful.
You can find the updater script at the following path: OreoSoak2.zip\META-INF\com\google\android\ or as an attachment.
As always, it's up to you if you want to flash these soak tests, bear in mind there may be bugs and unless you get the other soak test OTA updates, you may not be able to update back to the official OTA path. That is, unless you can find the stock Oreo fastboot ROM or try to downgrade. Or you could just wait for the official Oreo OTA to come out....
That's soak 3 buddy.
and the soak 2?
Possible to flash over SOAK 1 with bootloader locked?
ill try to install but the windows says "no such file or directory"
MiBan82 said:
Possible to flash over SOAK 1 with bootloader locked?
Click to expand...
Click to collapse
No you need the second one as well. You must install them in order that is why it is never smart to install a soak test unless you are in the test
xantanion said:
No you need the second one as well. You must install them in order that is why it is never smart to install a soak test unless you are in the test
Click to expand...
Click to collapse
Can we install it from 7.1.1?
eddiieeskt said:
Can we install it from 7.1.1?
Click to expand...
Click to collapse
If you've got the December 2017 7.1.1 update on your device, completely stock, you may be able to install these soak tests. However, as xantanion has pointed out, there appears to be at least one soak test OTA missing. Thus, you may be able to flash the first soak test OTA, then you may not be able to flash the soak test in this thread as you're not on the expected build for this OTA (i.e. you may be missing the inter-linking builds as again pointed out by xantanion). OTA updates check the build you have on your device before flashing, as I mentioned in the above post - this OTA requires OPN27.76-12-2 or OPN27.74 - if you don't have either, you may not be able to flash this OTA.
Without access to those possibly missing builds, you'd be stuck on an OTA build, and unless you find the Oreo fastboot stock ROM (which isn't out yet) or downgrading back to 7.1.1 (possibly risky, requires an unlocked bootloader), you likely won't be able to progress (no OTA updates) or not be able to flash the non-soak OTA builds. You'll only get these soak test OTA builds if you're part of the soak test program or someone can leak them.
You do not have to flash these soak test builds, you can always wait for the official OTA to arrive, unless you're willing to put up with the possible bugs in the firmware and the possibility that your device may not receive OTA updates.
EDIT - looks like some users may be having some luck with this OTA build?
echo92 said:
If you've got the December 2017 7.1.1 update on your device, completely stock, you may be able to install these soak tests. However, as xantanion has pointed out, there appears to be at least one soak test OTA missing. Thus, you may be able to flash the first soak test OTA, then you may not be able to flash the soak test in this thread as you're not on the expected build for this OTA (i.e. you may be missing the inter-linking builds as again pointed out by xantanion). OTA updates check the build you have on your device before flashing, as I mentioned in the above post - this OTA requires OPN27.76-12-2 or OPN27.74 - if you don't have either, you may not be able to flash this OTA.
Without access to those possibly missing builds, you'd be stuck on an OTA build, and unless you find the Oreo fastboot stock ROM (which isn't out yet) or downgrading back to 7.1.1 (possibly risky, requires an unlocked bootloader), you likely won't be able to progress (no OTA updates) or not be able to flash the non-soak OTA builds. You'll only get these soak test OTA builds if you're part of the soak test program or someone can leak them.
You do not have to flash these soak test builds, you can always wait for the official OTA to arrive, unless you're willing to put up with the possible bugs in the firmware and the possibility that your device may not receive OTA updates.
EDIT - looks like some users may be having some luck with this OTA build?
Click to expand...
Click to collapse
They're still going to have issues when it comes to updating to the full one even with being able to install it now via sideloading
Only two soak test are released over December security patch in India and they both are captured and shared on forum's
So when can we expect the actual update?
huma_dawii said:
So when can we expect the actual update?
Click to expand...
Click to collapse
I imagine it really is Motorola's decision, whenever they're happy with the build from internal testing and from the soak tester reports, and whether there are any major/show-stopping bugs still present or introduced. Minor bugs, depending on if they've been reported, may be fixed prior to the final OTA, or scheduled to be fixed in the post Oreo release if they're more troublesome to fix or troubleshoot. The soak test OTA may become the final OTA that's released to the general update channel, or there may be further OTA patches, which of course will push back the release date. The last thing you want is to introduce the Oreo update and then pull it, as happened with the Samsung Galaxy S8 devices.
So, it's anyone's guess when the release date will be, and why OEMs likely don't give hard deadlines, despite what the PR news release that's been on Ausdroid and other platforms suggests. At least you're getting a soak test - Moto G4 Plus/G5/G5S devices haven't seen one yet!
Please share the new apps.. dialer, camera, contacts
---------
I agree, you guys should ve happy for getting soal tests.. i have both G5+ and G5s+ and no soak tests.. we'll get oreo in may..
Pliss
Someone could kindly post all applications with new icons and the snaps manager ... thanks.
Aurich said:
Someone could kindly post all applications with new icons and the snaps manager ... thanks.
Click to expand...
Click to collapse
so far so good, I will see tomorrow how it`s performance
[email protected] said:
so far so good, I will see tomorrow how it`s performance
Click to expand...
Click to collapse
He meant a link to download the new apps without installing the soak test
--------------
Why moto dorsn't remove the buggy carrier name at the bottom lf the quick settings? With oreo we got that information at the top, no need to have it twice
Few mins ago Moto pushed February security patch for RETBR.
Download it here:
https://motoota.lolinet.com/index.p....26.241.15.addison.retail.en.US&carrier=retbr
You need to be on build NPNS26.118-22-2-12 to flash this update!
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
Just the security patch. Although islt coincided with the Oreo update in China. Let's hope that's in preparation for retbr Oreo.
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
I presume they will push Oreo in few hours.
rafikowy said:
I presume they will push Oreo in few hours.
Click to expand...
Click to collapse
That will be great. Even though I'll wait for a .xml.zip, on the one hand I accidentally did a downgrade (and I have no idea of the bootloader of September and December patch are different enough to cause bricking with OTAs) and I think my phone is due for a factory reset. It reboots very randomly and even though battery life is great I'm told it should be even better. Let's see if that does the fix
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
8cpaiw said:
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
Click to expand...
Click to collapse
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Artim_96 said:
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Click to expand...
Click to collapse
Hahahah true, but I'm still hoping for the best outcome
Already available for RETIN and RETUS. I'm guessing this is the last nougat patch, hopefully Oreo is next
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
You are 100% right :good:
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
If I'm reading the info in fastboot correctly, the Feb update does include an updated bootloader:
C1.14 (sha-a62b7ae, 2018-02-21 16:09:43)
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
SherlockDk said:
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
Click to expand...
Click to collapse
If the blankflashes in the other thread don't work, then you may either:
1)Have to wait for a newer blankflash to get leaked. These are Motorola internal development tools and as such aren't generally available - as they're also signed by Motorola, we may not be able to make them ourselves. The ones we have either came with the factory stock ROM or a leak from a generous Motorola engineer. You may be lucky and a blankflash may be included if an Oreo factory stock ROM comes out (not the usual fastboot ROM, a full factory image).
2)Have to pay to have your motherboard replaced, which seems to be 60-70% of the cost of a new device as far as I understand, so you may wish to put that money towards a new device instead.
I'm sorry I don't have better news, hard bricks are very difficult to resolve without the proper tools. You may wish to research making a loader image (a partition level copy of a working device, loaded onto an SD card), but it's not a definite rescue method.
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
fernseher said:
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
Click to expand...
Click to collapse
You will stay on RETEU. The link I provided is RETAIL version.
Hey can i use these files for my guide? This save me some time
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Bad url
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
If you still have that file, please upload it to androidfilehost or somewhere.
Did anyone from india received the update nd anyone had captured the OTA?
From what I've seen, this soak test OTA has been released in Brazil - it could come to India given that Brazil/India devices run on the NPN25.137-92 series of firmwares.
However, as with any soak test, flashing this soak test will take you off the official OTA path, meaning that you may not likely receive security or version updates at all (unless you are already part of the soak test and have been selected by the Motorola Feedback Network). If this is the only soak test update, you may get back onto official updates, but if there are subsequent OTAs released to soak testers, you'd be stuck. Thus, to get back onto the official updates, you'd have to downgrade back to stock Nougat, try to find all the soak tests in order, or wait for the official Oreo fastboot ROM. Also, with any soak test, you may experience bugs, even device bricking bugs, so be careful.
Have fun but please be responsible and be aware about what you're flashing to your device.
echo92 said:
From what I've seen, this soak test OTA has been released in Brazil - it could come to India given that Brazil/India devices run on the NPN25.137-92 series of firmwares.
However, as with any soak test, flashing this soak test will take you off the official OTA path, meaning that you may not likely receive security or version updates at all (unless you are already part of the soak test and have been selected by the Motorola Feedback Network). If this is the only soak test update, you may get back onto official updates, but if there are subsequent OTAs released to soak testers, you'd be stuck. Thus, to get back onto the official updates, you'd have to downgrade back to stock Nougat, try to find all the soak tests in order, or wait for the official Oreo fastboot ROM. Also, with any soak test, you may experience bugs, even device bricking bugs, so be careful.
Have fun but please be responsible and be aware about what you're flashing to your device.
Click to expand...
Click to collapse
Thanx for the information
But i m currently on custom rom nd if stable oreo is available I'll have tk wait for flashable zip file to flash it
karan3660 said:
Thanx for the information
But i m currently on custom rom nd if stable oreo is available I'll have tk wait for flashable zip file to flash it
Click to expand...
Click to collapse
Yup, so you'd likely have to revert back to the particular stock firmware required by this soak test (clean flash, so data wipe/possible internal storage wipe), then try to flash the soak test. Again, I've not seen any bug reports yet, but obviously if you flash this soak test and there are bugs, then you'll likely experience them....
echo92 said:
Yup, so you'd likely have to revert back to the particular stock firmware required by this soak test (clean flash, so data wipe/possible internal storage wipe), then try to flash the soak test. Again, I've not seen any bug reports yet, but obviously if you flash this soak test and there are bugs, then you'll likely experience them....
Click to expand...
Click to collapse
Okk lets wait for the stable oreo flashable zip ?