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
I have switched to a new device and no longer use this phone but i see many others facing this issue as well so I am keeping this thread open, please do not message me regarding the solution to this issue cause all i did to get out of this mess was getting a new phone.
Hello !
Due to some error while flashing stock rom on Moto G4 Plus XT-1643 my Moto G4 Plus has changed into Moto G4 but the model no shown in the "About Phone" section is correct.
I have lost one Imei no. fingerprint option is no where sim or mobile network doesn't work other than that the phone is fully functional(WiFi,Camers,Audio etc)
There are multiple threads on the same issue but no solution is available I would be highly grateful if anyone could find out any solution to this issue.
P.S : I have tried flashing multiple ROMs available on the forum specific to XT-1643 i.e Indian Version
Also I flashed the OTA file for the Android 7.0 Soak Test due to which I cannot relock the bootloader.
I am currently on Stock Marshmallow 6.0.1 139-63 Rooted&TWRP installed
The phone is basically an iPod without fingerprint sensor
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
this happened to my phone (1640 - brazilian moto g 4 plus), and I tried every single rom out there for moto g 4 plus, and it is only identified as Moto G 4, without fingerprint or any modem activity.
i still cannot recover previous bootloader, because it don't downgrade bootloader version. nothing worked for me so far.
i'll be watching this thread to see if anyone comes with any alternative.
sabithmk said:
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
Click to expand...
Click to collapse
Umm, so according to you too it's a software issue and not a hardware one right ?
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
if you flashed android 7.0 and then downgraded to android 6.0.1 then expect some bugs because your bootloader gets updated you have to do clean flash but you cannot actually completely downgrade to android 6.0.1 after you updated to 7.0 soak test bootloader still remains updated and your phone will brick when you click update after you receive 7.0 official OTA i warned you this happened to lot of moto x users do some research before you do anything if the phone is your primary device
Soureen said:
Umm, so according to you too it's a software issue and not a hardware one right ?
Click to expand...
Click to collapse
I think so. May be if we flash a wrong modem, the right one never flashes correctly. I don't know how do they managed to flash it correctly.
For me its a software issue... looks like it messed with the bootloader, and since you cannot rollback to an older bootloader, the phone works like an iPod Touch. haha
I hope that when Motorola releases the final 7.0 version for 1640, I'll be able to flash again the right bootloader and that will fix the phone.
SoNic67 said:
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
Click to expand...
Click to collapse
I did a full flash of an older 6.0.1 ROM, and it still doesn't work. Since the only thing that I couldn't flash is the bootloader, and the phone identify itself as Moto G 4 (and not Moto G 4 Plus) my guess is that the problem is with the bootloader.
I guess i'll have to wait for the official 7.0 for my specific phone (1640) to fully replace this broken bootloader.
Yeah, that's why I didn't upgrade to the N yet, I was sure that the bootloader will be different.
I also have saved the partitions with Partitions Backup & Restore app, after rooting.
Did you try the ElementalX kernel?
http://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
I was also having same issue,got my bootloader locked and went to service center and they replaced the motherboard for free????
Lucky you
Has anyone found a solution to get the plus (fingerprint) back to the phone?
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
That's a bummer but there might be some solution. The phone version number shouldn't be that hard to find if you'd knew witch file that flashes it.
How do you do these backups for they don't look at all as twrp backups so I guess twrp is second best to something. But what?
What is the different with 7.0 coming up? Can't you just relock a backup?
Soureen said:
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
Click to expand...
Click to collapse
I have the same issue, I have seen people with XT1643 having athene_f in build fingerprint but I have only athene. Which one is correct, could this be the issue?
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
m.swastik said:
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
Click to expand...
Click to collapse
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-63/64:user/release-keys
Click to expand...
Click to collapse
l2o88j said:
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
Click to expand...
Click to collapse
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
m.swastik said:
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
Click to expand...
Click to collapse
I found this trick early and I am using it now. I thought you cracked the last part (fingerprint sensor) which my post was about. I think that the issue is with gpt bin as I tried different bootloader versions along with all possible combinations. Gud to see someone else is working on the same. Will update if found any.
find the correct firmware for the device and flash it else it would lead to such errors
I had flashed the latest rr (nougat). I flashed stock firmware now and don't seem to have the notification for the nougat update. It says mty device is up to date, my one friend has recieved the update.
vaibhavplays said:
I had flashed the latest rr (nougat). I flashed stock firmware now and don't seem to have the notification for the nougat update. It says mty device is up to date, my one friend has recieved the update.
Click to expand...
Click to collapse
Which model no your device nd which stock rom you flash
a-2-k said:
Which model no your device nd which stock rom you flash
Click to expand...
Click to collapse
Yes the device model is xt1643 and the rom I flashed is the latest one MPJ24.139-63
vaibhavplays said:
Yes the device model is xt1643 and the rom I flashed is the latest one MPJ24.139-63
Click to expand...
Click to collapse
are you 100% confirm your friend recieve OTA for nougat
a-2-k said:
are you 100% confirm your friend recieve OTA for nougat
Click to expand...
Click to collapse
99% cause it could be soak test but he doesn't even know what recovery is so I don't think ke would have soak test on his phone
vaibhavplays said:
99% cause it could be soak test but he doesn't even know what recovery is so I don't think ke would have soak test on his phone
Click to expand...
Click to collapse
I think wait for some days to receive OTA Nougat bcz i don't think anyone got officially OTA Nougat...
I can confirm this. I had flashed MPJ24.139-63 earlier and received Nougat OTA Update. But since mine was rooted and had TWRP recovery, it failed. So I took the downloaded file and flashed MPJ24.139-63 again hoping I'd get the update. But now it tells my device is up to date.
Xt1644 RETUSA
This is nothing in plain sight for people in the United States as we get the chaft everytime. Good device but thought they followed Googles lead in their device updates. Here is what is received from Lenovo
My name is Mohammed from Motorola E-mail Support and it will be my pleasure to assist you with any concern that you might have. I hope that your day is going great so far.
Please accept my apologies for any inconvenience that we may have caused you.
In this case let me tell you that you can check for updates by going to Settings > About Phone> system updates. If the device says it's up to date, and you have not received the notification update, you should wait until the notification to arrive since it is sent via OTA, by the way let me tell you that we do not send system updates in this case you can also contact your carrier about this issue since they are in charge to send it.
I would also suggest you to please keep checking our software update page periodically:
https://motorola-global-portal.custhelp.com/app/software-upgrade-news/g_id/1949/https://motorola-global-portal.custhelp.com/app/software-upgrade-news/g_id/1949/
mikerowes69 said:
This is nothing in plain sight for people in the United States as we get the chaft everytime. Good device but thought they followed Googles lead in their device updates. Here is what is received from Lenovo
My name is Mohammed from Motorola E-mail Support and it will be my pleasure to assist you with any concern that you might have. I hope that your day is going great so far.
Please accept my apologies for any inconvenience that we may have caused you.
In this case let me tell you that you can check for updates by going to Settings > About Phone> system updates. If the device says it's up to date, and you have not received the notification update, you should wait until the notification to arrive since it is sent via OTA, by the way let me tell you that we do not send system updates in this case you can also contact your carrier about this issue since they are in charge to send it.
I would also suggest you to please keep checking our software update page periodically:
https://motorola-global-portal.custhelp.com/app/software-upgrade-news/g_id/1949/https://motorola-global-portal.custhelp.com/app/software-upgrade-news/g_id/1949/
Click to expand...
Click to collapse
I can't say for all carriers but I know that most have the final say on when the updates are pushed out. Since they field calls for problems their support people have to be up to speed on each release. Almost across the board you'll see the following when you put in your carrier "This device will be upgraded to the Android 7 (Nougat) release, pending partner support."
It sucks.
vaibhavplays said:
I had flashed the latest rr (nougat). I flashed stock firmware now and don't seem to have the notification for the nougat update. It says mty device is up to date, my one friend has recieved the update.
Click to expand...
Click to collapse
How to flash stock MM firmware from latest NPJ25.93-11 Nougat firmware? Please help.
I am also waiting for the N update...I thought moto is good at delivering Android updates... and now I'm running out of patience...
Has anybody received Nougat update on Moto g4 plus in India yet
Sent from my Moto G (4) using Tapatalk
I am a beginner and wanted to know if I can iodatey G4 plus with the ota zips available online. My device is extremely new and I don't want to take any risk or void the warranty. Any suggestions! Maybe I could wait for the official update to come? Pls help.
prateekk056 said:
I am a beginner and wanted to know if I can iodatey G4 plus with the ota zips available online. My device is extremely new and I don't want to take any risk or void the warranty. Any suggestions! Maybe I could wait for the official update to come? Pls help.
Click to expand...
Click to collapse
The only way to remain risk free let the update notification arrive and then update from there. Anything else has an element of riskiness involved.
But soak test otas can be flashed if you can bear the risk
guessingagain said:
The only way to remain risk free let the update notification arrive and then update from there. Anything else has an element of riskiness involved.
But soak test otas can be flashed if you can bear the risk
Click to expand...
Click to collapse
Ok thanks!
Is there such a problem with waiting? I mean really? If you are so desperate for an upgrade install a custom ROM. It's not officially released yet and only reports of soak tests are not through Motorola. Please be patient. It's better to have it right than not.
daverobinson88 said:
Is there such a problem with waiting? I mean really? If you are so desperate for an upgrade install a custom ROM. It's not officially released yet and only reports of soak tests are not through Motorola. Please be patient. It's better to have it right than not.
Click to expand...
Click to collapse
My thoughts exactly. I can see the point if someone wants to install a custom rom, lord knows I've done it enough, but installing a soak test that could kill your real OTA or contain bad code, borders on ridiculous. If you don't have a chance of receving Nougat then I'd go for it, but AFAIK, all the G4's are going to get it. I actually had an official soak test on a previous phone and it killed my final ota.
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
Hello,
I've just bought a second-hand moto G5 Plus that had a custom rom installed on it, I'm guessing it was also rooted at some point. It currently has the Aug 1 2018 version of 8.1:
build #: OPS28.85-13
It's been a while since I've messed about with flashing phones, so I wanted to ask for some assistance before potentially bricking the poor thing.
Ideally, I'd like to get it back on the stock update channel, so it can get OTA updates, but with root -- if that's not possible, I'd be almost as happy to just flash a Sept 1 2018 build (which my other 100% stock G5 plus already has) and root it. I've looked at a few posts here, notably this one:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Though not knowing the exact history of the device, I'm reluctant to just follow the instructions. Can anyone provide some insight as to the safe(st) procedure?
Thanks!
-pir
You can't have root and receive updates from official channel at the same time.. the bootloader need to be locked to recieve updates.. you can however flash twrp on the device.. flash the stock rom( you will find latest in the forums).. and when the updates come out someone will capture it and make a flashabe zip, so you just need to flash that.. you can have root that way and stay updated.. cause from what I've read so far you don't get OTA when you're bootloader is unlocked..
That makes sense. So I guess the moto software won't even attempt an update if the bootloader is unlocked? Thanks!
Unlocked bootloader won't make any difference. The OTA update checks the system files and bootloader. If you have made any modifications to the system, kernel, or are running an older bootloader version the update will fail. Lock status of the bootloader makes no difference.
Sent from my Moto G (5) Plus using Tapatalk