Related
Hey folks, I created this thread just to separate this version of 4.4.4 which can't update to Lollipop using the current OTA file outhere. So I ask if someone which have this version receive the update to try to capture and share with the people.
Currently the only way to downgrade as I understand is downgrade the firmware to the KXB21.85.23 but for this you need to unlock bootloader, which will make you loose your warranty. So for people like me stuck with this version please you this thread to don't generate more doubts in the other threads. If you have other ways to downgrade without unlocking bootloader please share!
Best regards!:good:
same here stuck at .27
Is there any overview which software Version Runs on which xt106x hardwareversion and on which Country Variant?
There were that much discussions of Different version combinations that i am probably not the only one who has lost the overview..?
This KitKat version was never an official OTA. So you can't upgrade from this version. Officialy you can't have it. Downgrade to .23 and you'll be fine!
Edit:
About loosing your warranty: you've installed the .27 update with een unlocked bootloader. So your warranty was already void. Relocking your bootloader brought it to 'Status 2' meaning you had it unlocked in the past. Never unlocked is 'status 0'. You never will get your warranty back by relocking it.
I tried it not working
smitharro said:
This KitKat version was never an official OTA. So you can't upgrade from this version. Officialy you can't have it. Downgrade to .23 and you'll be fine!
Edit:
About loosing your warranty: you've installed the .27 update with een unlocked bootloader. So your warranty was already void. Relocking your bootloader brought it to 'Status 2' meaning you had it unlocked in the past. Never unlocked is 'status 0'. You never will get your warranty back by relocking it.
Click to expand...
Click to collapse
impossible to downgrade to 0.23 without unlocking your bootloader
adel pro said:
impossible to downgrade to 0.23 without unlocking your bootloader
Click to expand...
Click to collapse
That's what I said! It was impossible to instal .27 without a locked bootloader, downgrading with a locked bootloader is also impossible!
smitharro said:
That's what I said! It was impossible to instal .27 without a locked bootloader, downgrading with a locked bootloader is also impossible!
Click to expand...
Click to collapse
so we might recive the taste of official lollipop or not on .27 via ota on locked BL?? @smitharro
smitharro said:
This KitKat version was never an official OTA. So you can't upgrade from this version. Officialy you can't have it. Downgrade to .23 and you'll be fine!
Edit:
About loosing your warranty: you've installed the .27 update with een unlocked bootloader. So your warranty was already void. Relocking your bootloader brought it to 'Status 2' meaning you had it unlocked in the past. Never unlocked is 'status 0'. You never will get your warranty back by relocking it.
Click to expand...
Click to collapse
I bought a motog 1 month ago, i'm running stock, and the version that came instaled was in fact 21.11.27.titan_retaildsds.retaildsdsall.en.03reteu, KX21.85-27, it may not have been an ota but it is at least official, it came factory instaled. So, you are wrong...
fastmugen88 said:
I bought a motog 1 month ago, i'm running stock, and the version that came instaled was in fact 21.11.27.titan_retaildsds.retaildsdsall.en.03reteu, KX21.85-27, it may not have been an ota but it is at least official, it came factory instaled. So, you are wrong...
Click to expand...
Click to collapse
OK, possible... Where did you buy your phone and, more important, what is the bootloader status? If the bootloader status is 0, then you're right and I am wrong. If it's 2, then your bootloader has been unlocked in the past!
smitharro said:
OK, possible... Where did you buy your phone and, more important, what is the bootloader status? If the bootloader status is 0, then you're right and I am wrong. If it's 2, then your bootloader has been unlocked in the past!
Click to expand...
Click to collapse
Bought new from Fnac in Portugal on Dec. the 16th. How do I check the bootloader status?
Please note that i'm not a devoloper, so I don't know this things deeply, but I do know what is an OTA, factory images, root...etc, meaning I Know that I haven't unlocked or rooted the smartphone.... that's why I'm telling that .27 is official, probably came preinstaled in the latest batch for EMEA region.
fastmugen88 said:
Bought new from Fnac in Portugal on Dec. the 16th. How do I check the bootloader status?
Please note that i'm not a devoloper, so I don't know this things deeply, but I do know what is an OTA, factory images, root...etc, meaning I Know that I haven't unlocked or rooted the smartphone.... that's why I'm telling that .27 is official, probably came preinstaled in the latest batch for EMEA region.
Click to expand...
Click to collapse
1 - Shut down phone completely
2 - Press Vol down + power for 5 seconds
3 - Release both keys and device will boot up to fastboot mode where you can see this.
@smitharro
Got my device last week.
On .27
Device is LOCKED. Status Code: 0
pakatus said:
1 - Shut down phone completely
2 - Press Vol down + power for 5 seconds
3 - Release both keys and device will boot up to fastboot mode where you can see this.
@smitharro
Got my device last week.
On .27
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
Okay, my bad then! I was wrongly informed! So just wait and the lollipop OTA should be released in a while!
Send from my XT1068 using Tapatalk.
The main difference in this version is coming with more languages support, as I said we are stuck in this version and of course I'm not thinking in unlocking the bootloader because in case of something goes wrong in the phone I could have the luck of Amazon trade for another new or sent to Motorola and there I'am screwed ...
If someone Find anyway possible without have to unlock the bootloader fire it out!
same here...i guess we have to wait.
Actually 27 is an incremental update. Motorola has updated Moto G 2014 software page with the details.
Google launcher was update and some minor improvements.
My one was bought 2 weeks ago in Poland.
And 27 was preinstalled.
well, im in the same boat,
was using the xt 1063 version lollipop then migrated back to 4.4 stock
stuck on .24 titan retbr ds retbr en br oi br
So with the news of today saying will roll out the new update for lollipop any one if have this version and bootloader unlocked can make a favor of post here the file for this Version?
keb00 said:
So with the news of today saying will roll out the new update for lollipop any one if have this version and bootloader unlocked can make a favor of post here the file for this Version?
Click to expand...
Click to collapse
Humm... i think the official OVA that was released today it's only for version .23 (Brazil, India and US) and probably the same version of soak tests, but we will see
24/01 and still no OTA update for my xt1068 in France (phone bought on amazon, having a reteu firmware)
@oiej47 same here stuck at .27
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
inFiniTyz_Z said:
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
Click to expand...
Click to collapse
If you wish to simply re-lock your bootloader, the easiest thing is to flash this fastboot stock ROM (which is Nougat) and use the locking script as directed in the first post. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this may wipe your data - so back up, and the relocking may or may not work, in which case you may have to wait for a more up to date fastboot stock ROM to become available.
If you were to downgrade to Marshmallow, you cannot downgrade your bootloader and GPT partitions, at best, your existing bootloader would try to prevent you from downgrading those partitions. At worst, you'll brick your device again if you were to flash those - though we've got possible ways of fixing that, it's not a route I'd want to go down. Flashing the rest of Marshmallow is no problem, however, ensure you have the correct MM firmware for your device and territory.
Will this version work for my country(Germany) without OTA trouble?
inFiniTyz_Z said:
Will this version work for my country(Germany) without OTA trouble?
Click to expand...
Click to collapse
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
echo92 said:
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
Click to expand...
Click to collapse
THANK YOU IT WORKED AND THE WARNING DISAPPEARED. I am on Nougat, locked and its working like a charm
I WOULD KISS YOUR BUTT IF ITS HAVE TO BE
I was in B.05 version (the one of the 14-4 update) and i flashed the (soak test?) -11 build, with bootloader,partitions and everything, i was hopping the bootloader didn't flash (like always showing error) , but it did,it flashed the bootloader, and now i'm in B0.3 version, and the phone didn't brick, i thought it wasn't possible....!!
I'm happy because i was looking for a way to downgrade the bootloader, but i never thought to do it like that.......
What do you think??
UPDATE: NOW, i flashed Marshmallow firmware and the bootloader downgraded correctly. i have had flashed marshmallow before, and it gave me an error, but now it flashed and now i'm in B0.0E version....
HOW?!?!?
If it's the 93-11 build, that's not a soak test - that was the first of the official Nougat updates (though only formally released in India if I recall - so in other territories you may not get any OTA updates).
Regardless, as I understand it, downgrading your bootloader may not brick your device - what may brick your device is downloading and updating via OTA updates subsequently.
By the way, what was the reason for wanting to downgrade your bootloader? If you wanted to downgrade your system, you could have just flashed Nougat or Marshmallow, just not flashing the GPT or bootloader partitions.
The reason is that i want to update by ota from marshmallow to nougat to get a smooth nougat, because if i flash it with fastboot it has got a lot of lag (i don't know why, but is very noticeable)
I just updated from 6.0 to 7.0 (-14) so it really downgraded the bootloader.
So if someone else want to downgrade the bootloader, you can flash -11 bootloader!!
Update. Again; flashed marshmallow firmware and bootloader downgraded too. What is going on??
ivan290 said:
Update. Again; flashed marshmallow firmware and bootloader downgraded too. What is going on??
Click to expand...
Click to collapse
Fastbooting Marshamallow will include Bootloader partition by default--you have to skip bootloader flashing to NOT downgrade bootloader. N bootloader will work fine with Marshmallow.
Now i updated to 14-8 version (B.06 bootloader version) (June patch) and i CAN'T downgrade my bootloader anymore, even flashing -11, marshmallow, or any other firmware.. Strange
ivan290 said:
Now i updated to 14-8 version (B.06 bootloader version) (June patch) and i CAN'T downgrade my bootloader anymore, even flashing -11, marshmallow, or any other firmware.. Strange
Click to expand...
Click to collapse
Possibly to prevent users from downgrading and opening up the security vulnerability that was patched in the May 2017 security update. https://alephsecurity.com/2017/05/23/nexus6-initroot/ https://www.xda-developers.com/moto...a-root-shell-patched-in-mays-security-update/
At any rate, seems that other users trying to downgrade their bootloader from B1:06 hard bricked (and the blankflash we have doesn't appear to function). Be careful.
echo92 said:
Possibly to prevent users from downgrading and opening up the security vulnerability that was patched in the May 2017 security update. https://alephsecurity.com/2017/05/23/nexus6-initroot/ https://www.xda-developers.com/moto...a-root-shell-patched-in-mays-security-update/
At any rate, seems that other users trying to downgrade their bootloader from B1:06 hard bricked (and the blankflash we have doesn't appear to function). Be careful.
Click to expand...
Click to collapse
I tried it, and now it just seems to have become a paperweight from the june patch.
As you mentioned the blank files are also not working, what should I do now:crying::crying:
echo92 said:
Possibly to prevent users from downgrading and opening up the security vulnerability that was patched in the May 2017 security update. https://alephsecurity.com/2017/05/23/nexus6-initroot/ https://www.xda-developers.com/moto...a-root-shell-patched-in-mays-security-update/
At any rate, seems that other users trying to downgrade their bootloader from B1:06 hard bricked (and the blankflash we have doesn't appear to function). Be careful.
Click to expand...
Click to collapse
Oh!! Thank you, now i understand everything.... Thank you man!
I am having xt1686 indian variant .. i unlocked the bootloader and installed the custom roms.. now while going back to stock i mistakenly installed NPNS (US VARIANT, I suppose) ..
I am unable to install the NPN version now .. i guess the bootloader is not matching ..
Right now i am having a bootloader - C0.8(*) in NPNS ...
PLEAAE SUGGEST HOW TO MOVE TO INDIAN VERSION OF NPN... THNKS..
S does not mean US or any other variant specific build... there are literally different builds for different variants. My US Retail version is NPN25.173-83
In previous Moto models, the S meant it had been upgraded from an OTA, but in looking in my current device it has received several OTAs and does not have the S, so either that has been depreciated or our original assumptions in earlier models was incorrect.
Either way, the fact the S is there does not mean US (or any other country), just a slightly different build... I don't have an answer of why you can't go back though.
https://forum.xda-developers.com/g5-plus/help/npns-nps-firmware-t3677576
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
abhi.a3s said:
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
Click to expand...
Click to collapse
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. If you've flashed a NPNS firmware, you'd likely be at least on the may security patch. The Indian firmware you'd need is the January patch (NPN25.137-15, as I don't think the NPN25.137-67 or 67-5 firmwares have been leaked). Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
echo92 said:
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
Click to expand...
Click to collapse
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
abhi.a3s said:
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
echo92 said:
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Click to expand...
Click to collapse
Well ofcourse there is a big potential of hard bricking the device by the method. That's why I said last resort.
So what do you suggest?
TWRP image? And if it doesn't work, he should probably wait up for next NPN build? @toyesh.patra you should consider keeping a custom rom if possible.
Btw
The ota update which I received was August patch. After which I unlocked my bootloader. It was either NPN25.137-67 or NPN25.137-67-5. I'M not sure about version. But it was definitely August patch.
Or maybe I was lucky one time.
Won't do it another time.
anuraag.neo said:
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
Click to expand...
Click to collapse
For 1686? Full fastboot firmware leaked?
yea, right now i m using the 67-5 build using twrp..
although i wanted to use the 67-5 with locked bootloader.. nevermind ..
psychopac said:
For 1686? Full fastboot firmware leaked?
Click to expand...
Click to collapse
Yes
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
psychopac said:
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
Click to expand...
Click to collapse
Yes
I can't download it. How Can I download? please upload googel Thanks bro
birkhoffChang said:
I can't download it. How Can I download? please upload googel Thanks bro
Click to expand...
Click to collapse
use search function before asking
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
Moto g4 plus (xt1643)
No software update received
Need help
mj.mhatre said:
Need help
Click to expand...
Click to collapse
Can you please write more then those words? Which device model, rom version you are currently?
What update did you need? Which carrier, baseband and country?
Thanks!
Moto g4 plus (xt1643)
Android security patch- 1 Oct. 2016
Build number -NPJ25.75-2
Stuck update
mj.mhatre said:
Moto g4 plus (xt1643)
Android security patch- 1 Oct. 2016
Build number -NPJ25.75-2
Stuck update
Click to expand...
Click to collapse
I think you haven't written build number correctly ?
Can you put screenshot of "about phone" ?
Have you ever flashed stock ROM in past year ?
UPDATE:
That's nougat soak version !! Right ?
Nougat soak update haven't got any update, you have to flash updated official firmware yourself.
See link for how to flash latest September's security update : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
mj.mhatre said:
Moto g4 plus (xt1643)
Android security patch- 1 Oct. 2016
Build number -NPJ25.75-2
Stuck update
Click to expand...
Click to collapse
you have probably flashed the soak test of android 7.0 over 6.0
Motorola have clearly said the people who have flashed soak test manually will not get OTA updates
the only way to get updates is flash the stock rom via fastboot..
siddhesh9146 said:
you have probably flashed the soak test of android 7.0 over 6.0
Motorola have clearly said the people who have flashed soak test manually will not get OTA updates
the only way to get updates is flash the stock rom via fastboot..
Click to expand...
Click to collapse
Not unlocking bootloader I try
mj.mhatre said:
Not unlocking bootloader I try
Click to expand...
Click to collapse
Yeah..to flash the stock rom via fastboot you dont have to unlock your bootloader. And please make sure you are flashing the latest rom that is mentioned in the above reply.