Related
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
Sorry for the stupid question. I have checked in the system settings for a new update but it says I'm on the latest patch. I've also heard that there may not even be a security patch available for the retail US XT1625 and it should still be on MPJ24.139-48, is that true?
I've checked the Motorola website and it seems there is an update that I don't have. I don't really know what I'm doing and I don't want to void my warranty by flashing a newer stock image, if that even does void it.
If there's anything I can do, I would appreciate the help. Thank you.
NDS02 said:
Sorry for the stupid question. I have checked in the system settings for a new update but it says I'm on the latest patch. I've also heard that there may not even be a security patch available for the retail US XT1625 and it should still be on MPJ24.139-48, is that true?
I've checked the Motorola website and it seems there is an update that I don't have. I don't really know what I'm doing and I don't want to void my warranty by flashing a newer stock image, if that even does void it.
If there's anything I can do, I would appreciate the help. Thank you.
Click to expand...
Click to collapse
No, MPJ24.139-64 is the latest stock firmware. Not sure why you aren't getting it, unless you are on a custom recovery. That would prevent you from getting the update. I too have the XT1625 and I had to return my device to stock recovery before I received the update. There is a thread somewhere in the forum (might be in G4+) that tells you how.
However, if you are on full stock with no modifications then I have no idea why you aren't getting it.
I am indeed on full stock, I just bought this phone factory unlocked last week from a retail store and I really don't know why I haven't received an update for it. Is there any way that I can force it to update without unlocking the bootloader and just flashing the new stock image? I want to receive the Android 7.0 update when that comes out, but I would also like to update to the most recent build.
Can I sideload the OTA without voiding my warranty and also still get the Android N update when it becomes available? If so how?
If you have any answers I would greatly appreciate them.
NDS02 said:
I am indeed on full stock, I just bought this phone factory unlocked last week from a retail store and I really don't know why I haven't received an update for it. Is there any way that I can force it to update without unlocking the bootloader and just flashing the new stock image? I want to receive the Android 7.0 update when that comes out, but I would also like to update to the most recent build.
Can I sideload the OTA without voiding my warranty and also still get the Android N update when it becomes available? If so how?
If you have any answers I would greatly appreciate them.
Click to expand...
Click to collapse
If you are 100% certain the bootloader is still locked then the only thing I can suggest is to contact Motorola Customer Service and find out why it isn't updating. Or return to the store where you purchased it. But my phone downloaded the update even before I returned to stock recovery. I then saved it to my SDCard, returned to stock, and put the update back in the proper folder. When I rebooted it updated the normal way. Was it unopened when you bought it? Maybe the store did something to affect the update. Also, I am on the USA version and assume you are as well.
It is a USA version.
I already called Motorola customer service and they said that the Moto G4 receives updates in batches and that whether or not I receive the security update is based entirely on my carrier. I have Straight Talk AT&T. I've also tried it with a Sprint SIM card and it didn't update either.
When I brought it back to the store I purchased it from (Best Buy), they said that since it's an unlocked phone it will receive updates directly from Motorola, and it doesn't matter what carrier it's on.
NDS02 said:
It is a USA version.
I already called Motorola customer service and they said that the Moto G4 receives updates in batches and that whether or not I receive the security update is based entirely on my carrier. I have Straight Talk AT&T. I've also tried it with a Sprint SIM card and it didn't update either.
When I brought it back to the store I purchased it from (Best Buy), they said that since it's an unlocked phone it will receive updates directly from Motorola, and it doesn't matter what carrier it's on.
Click to expand...
Click to collapse
Best Buy is correct. As far as Motorola Customer Service, the answer one gets from to any question depends on who you ask. I have never had to call them, but other users here on XDA have had a wide variety of results. Sometimes calling back and trying a different rep yields better results. Maybe clarifying your phone model/type and the fact you have an unlocked phone would help.
Other than that my friend, I am out of suggestions.
I'm also still on -48. Purchased from Costco.
Sent from my Moto G (4) using Tapatalk
NDS02 said:
Sorry for the stupid question. I have checked in the system settings for a new update but it says I'm on the latest patch. I've also heard that there may not even be a security patch available for the retail US XT1625 and it should still be on MPJ24.139-48, is that true?
I've checked the Motorola website and it seems there is an update that I don't have. I don't really know what I'm doing and I don't want to void my warranty by flashing a newer stock image, if that even does void it.
If there's anything I can do, I would appreciate the help. Thank you.
Click to expand...
Click to collapse
From all the threads and surfing on different sites I have come to a conclusion that the MPJ24.139-63/64 updates is only for amazon variant , because on the official Motorola site the said update is only for amazon variant . And the latest for non-amazon is the MPJ24.139-48/49
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Mansuur said:
From all the threads and surfing on different sites I have come to a conclusion that the MPJ24.139-63/64 updates is only for amazon variant , because on the official Motorola site the said update is only for amazon variant . And the latest for non-amazon is the MPJ24.139-48/49
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Not sure why you came to that conclusion, but you are dead wrong. I do not have the Amazon variant and I received the update to MPJ24.139-64 via the normal update channel from Motorola. Also, here is a link to the Non-Amazon variant of the stock ROM (-64 version):
http://www.filefactory.com/file/3sqq...LT_CFC.xml.zip
Furthermore, I have a copy of the -64 update blur file (non-Amazon variant) saved to my PC.
Any questions?
Can you share the blur file update?
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
pastorbob62 said:
Not sure why you came to that conclusion, but you are dead wrong. I do not have the Amazon variant and I received the update to MPJ24.139-64 via the normal update channel from Motorola. Also, here is a link to the Non-Amazon variant of the stock ROM (-64 version):
http://www.filefactory.com/file/3sqq...LT_CFC.xml.zip
Furthermore, I have a copy of the -64 update blur file (non-Amazon variant) saved to my PC.
Any questions?
Click to expand...
Click to collapse
Can you share the blur file update?
pastorbob62 said:
Not sure why you came to that conclusion, but you are dead wrong. I do not have the Amazon variant and I received the update to MPJ24.139-64 via the normal update channel from Motorola. Also, here is a link to the Non-Amazon variant of the stock ROM (-64 version):
http://www.filefactory.com/file/3sqq...LT_CFC.xml.zip
Furthermore, I have a copy of the -64 update blur file (non-Amazon variant) saved to my PC.
Any questions?
Click to expand...
Click to collapse
Okay , but a lot of Moto G4 users are still on MPJ24.139-48 and not getting the update , especially the ones who are on MPJ24.139-49 . I have not read a single comment from a MPJ24.139-49 user that he/she got the july patch to MPJ24.139-63/64 .
There is a person on the official Lenovo Motorola forums where he wrote that he bought two devices from the same retailer and one of the devices got the update immediately to MPJ24.139-64 but the other one is still stuck on MPJ24.139-49 . Can you help me with that .
I have tried to install the blur files available on the forums but it gives the error because the update is for 139-48 users not 139-49 ones . I have also tried to install the Full Stock MPJ24.139-64 but still gives the " wrong footer " error .
Thanks !
Mansuur said:
Okay , but a lot of Moto G4 users are still on MPJ24.139-48 and not getting the update , especially the ones who are on MPJ24.139-49 . I have not read a single comment from a MPJ24.139-49 user that he/she got the july patch to MPJ24.139-63/64 .
There is a person on the official Lenovo Motorola forums where he wrote that he bought two devices from the same retailer and one of the devices got the update immediately to MPJ24.139-64 but the other one is still stuck on MPJ24.139-49 . Can you help me with that .
I have tried to install the blur files available on the forums but it gives the error because the update is for 139-48 users not 139-49 ones . I have also tried to install the Full Stock MPJ24.139-64 but still gives the " wrong footer " error .
Thanks !
Click to expand...
Click to collapse
I have no idea. All I know is that my XT1625 16 Gbyte USA version updated without any issues from -48 to -64 (back in October). The -49 version is a completely different animal (maybe the G4+) and I have no experience with it. You might check your Software Channel under Settings/About Phone and see which one you are on (I am on the retus Software Channel), but other than that I have no clue, unless the version hardware is different.
Again, you are talking apples and oranges when referring to the -49 version.
pastorbob62 said:
I have no idea. All I know is that my XT1625 16 Gbyte USA version updated without any issues from -48 to -64 (back in October). The -49 version is a completely different animal (maybe the G4+) and I have no experience with it. You might check your Software Channel under Settings/About Phone and see which one you are on (I am on the retus Software Channel), but other than that I have no clue, unless the version hardware is different.
Again, you are talking apples and oranges when referring to the -49 version.
Click to expand...
Click to collapse
Hahahaha .....
Mine is also ( G4 )ATHENE XT1625 RETUS version , not ( G4+ ).
Available firmware versions for XT1625 are :
MPJ24.139-48
MPJ24.139-49 , and
MPJ24.139-64 . You can check on https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
For some reason a some users got update from -48 to -64 and some got -48 to -49 and got stuck with it . I do not know what is going on . Just hoping to get the NOUGAT UPDATE . I am also very confused about the number system .
I would love to keep this thread going. I am in the same boat. I have a Moto G4 (Non-Plus) XT1625 Retus version. I am still on MPJ24.139-48. If you review Motorola's website...it says the latest version available is MPJ24.139-64. However, I have never received this OTA update. As a matter of fact I have tried to install this firmware from their website before and while it installs I get error crashes.
As far as I can tell from my research, in the US... some users got 64 but a lot of people are still on 48. Any thoughts? I would love to get this solved. Oh! and before you ask NO i don,t own the amazon variant!
30mmrain said:
I would love to keep this thread going. I am in the same boat. I have a Moto G4 (Non-Plus) XT1625 Retus version. I am still on MPJ24.139-48. If you review Motorola's website...it says the latest version available is MPJ24.139-64. However, I have never received this OTA update. As a matter of fact I have tried to install this firmware from their website before and while it installs I get error crashes.
As far as I can tell from my research, in the US... some users got 64 but a lot of people are still on 48. Any thoughts? I would love to get this solved. Oh! and before you ask NO i don,t own the amazon variant!
Click to expand...
Click to collapse
If you are on 139-48 try this OTA update .
https://forum.xda-developers.com/moto-g4/help/amazon-xt1625-ota-t3474128
Mansuur said:
If you are on 139-48 try this OTA update .
https://forum.xda-developers.com/moto-g4/help/amazon-xt1625-ota-t3474128
Click to expand...
Click to collapse
Good news this image worked! I am not on mpj25.139-64 :good: thanks.
Now on to the next problem... Relocking the bootloader. Ever since I unlocked it the first time... I have not been able to lock it. It errors out and asks for an official signed image. Which confuses me... Since ever one I've installed (minus the custom Roms ) have been. If anyone here has suggested fix let me know... Otherwise. I'll create another thread so I don't hijack this one.
Thanks again
30mmrain said:
Good news this image worked! I am not on mpj25.139-64 :good: thanks.
Now on to the next problem... Relocking the bootloader. Ever since I unlocked it the first time... I have not been able to lock it. It errors out and asks for an official signed image. Which confuses me... Since ever one I've installed (minus the custom Roms ) have been. If anyone here has suggested fix let me know... Otherwise. I'll create another thread so I don't hijack this one.
Thanks again
Click to expand...
Click to collapse
For that you have to install full stock/factory image which will re-lock your bootloader . But , that will erase all of your data . You can find tutorials on forum , no need to create another thread .
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
Mansuur said:
For that you have to install full stock/factory image which will re-lock your bootloader . But , that will erase all of your data . You can find tutorials on forum , no need to create another thread .
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
Click to expand...
Click to collapse
When I was on mpj24.139-48... I tried flashing the full image downloaded from Motorola's site. Still ran into the same issue. I don't mind that it will wipe my data.
On that link you sent over. Which file to download? I see the xt1625 folder and I see the Amazon firmware in it... But I am unsure what the other firmware is. I also see the Athens mpj25.139-64 folder on the main page below. Which is the safe file?
Thanks
30mmrain said:
When I was on mpj24.139-48... I tried flashing the full image downloaded from Motorola's site. Still ran into the same issue. I don't mind that it will wipe my data.
On that link you sent over. Which file to download? I see the xt1625 folder and I see the Amazon firmware in it... But I am unsure what the other firmware is. I also see the Athens mpj25.139-64 folder on the main page below. Which is the safe file?
Thanks
Click to expand...
Click to collapse
Try the the one with this name " XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip " .
Have you tried flashing through fastboot mode ?
Mansuur said:
Try the the one with this name " XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip " .
Have you tried flashing through fastboot mode ?
Click to expand...
Click to collapse
Yeah minus... The custom Roms that is where I have always been flashing. On the custom side of things I was using TWRP.
Alright... I will try flashing the file is suggest and I'll post back here shortly
Hi guys,
I got a Pixel replacement for my Nexus 6P, love the phone but missed the larger screen so selling it and bought second hand Pixel XL with 2 year warranty from CeX.
I noticed when it booted it said something about not running the initial Firmware. I asked the shop as was sold as the "unlocked" version. They told me was ee but genuine firmware that unlocked the phone and will function no differently and receive all updates without delay.
Having set up the phone, it's still running 7.1 and not detecting anything newer. Plus security patches are 05/10/16. This seems like a problem.
Do I need to return it?
EDIT: just started WhatsApp which told me I have a custom ROM which child cause issues. I bought the pixel to have native android.
Many thanks,
Max
Just flash the latest firmware
Sent from my Le X526 using Tapatalk
Thanks for the reply. But will I have to do this for every update and also to get security patches?
Just realised I'm in the wing sub forum. Can I ask to have it move?
maxcovergold said:
Thanks for the reply. But will I have to do this for every update and also to get security patches?
Just realised I'm in the wing sub forum. Can I ask to have it move?
Click to expand...
Click to collapse
No, you shouldn't have to flash every update once you are on official images. Just flash the stock Google images and you should be good to go. https://developers.google.com/android/images
calripkenturner said:
No, you shouldn't have to flash every update once you are on official images. Just flash the stock Google images and you should be good to go. https://developers.google.com/android/images
Click to expand...
Click to collapse
I noticed in the FAQ about meeting through boot loader unlocked and not relocking it. Presumably it must have been unlocked to change the original Firmware, but I don't get that message "Your device software can't be checked for corruption. Please lock the bootloader".
Is this going to be a problem in fishing the firmware? Sorry, I bought the Pixel as I really have no idea about the things, want exciting this.
The sign is just shown that your bootloader is unlocked.
My Moto G5 Plus is telling me that my software is up to date, yet it's still running Android 7.0, but more importantly the security patch level is 1/1/17. I don't know about major OS updates, but there MUST be at least some updates out there that I'm not getting. Can someone link me to somewhere where I can find a .zip files for all OTA updates, so I can just flash the update and then flash Magisk again to retain root? Thanks!
You are probably not receiving OTA updates since you've rooted your phone, right? There was no major updates but there was few security patches this year. Which model exactly you have? That's gonna help in providing you correct links...
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
nlinecomputers said:
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
Click to expand...
Click to collapse
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
acejavelin said:
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
Click to expand...
Click to collapse
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
nlinecomputers said:
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
Click to expand...
Click to collapse
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
acejavelin said:
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
Click to expand...
Click to collapse
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
nlinecomputers said:
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
Click to expand...
Click to collapse
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
FamilyGuy0395 said:
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
Click to expand...
Click to collapse
Sort of... OTA files can only be flashed on a pure stock system, no root, no TWRP, no Xposed, nothing changed in system, no removed packages, etc. If the OTA script even detects that /system was ever mounted R/W it can fail (I don't know if Moto goes that far).
To flash an OTA you must restore your stock ROM completely (/system, /boot, and any other system level partitions), and restore stock recovery, and all versions must match or the OTA script will crap out with an error.
The OTA files are out there, on this forum in various threads... you can find them along with instructions on how to apply them to rooted and stock systems.
acejavelin said:
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
Click to expand...
Click to collapse
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
nlinecomputers said:
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
Click to expand...
Click to collapse
Oh yeah... Moto's level of doing what the carriers "recommend" or whatever you want to call it, is ridiculous lately.
Good example is Nougat for the Moto X Pure Edition, if you are on Sprint or US Cellular you got it 2 months ago, but Verizon, AT&T, and T-Mobile users still haven't seen it. Except many users have figured it out, pop in a Boost Mobile SIM (not even activated) and it will grab the update almost immediately, let it apply, then swap your original SIM back in and enjoy some Nougat goodness. However that device never had a specific version for a certain carrier. Still today probably 80% of users of that FLAGSHIP device still haven't gotten an update that we know was completed in June/July, due to "partner approvals" or some such BS.
All these updates still come directly from Moto and their servers, but they are doing what the carriers tell them and only allowing it to certain devices... This has vaguely been admitted to by the mods on the official Lenovo support forums.
Honestly, many smaller brands with a history of poor update frequency get better update support than Moto's these days... My son's Axon 7 Mini already has 7.1.1 with the September update for BlueBourne, he got it the third week of September, and gets on every 3 months like clockwork. My faith in Moto is diminishing quickly, I gave them the benefit of the doubt on my last two (Moto X Pure Edition and Moto G 2015) because they were kind of transitional device during the Google-Lenovo switch over, and although my Moto G5 Plus is supported a little better I believe it is just because it is newer and not because Moto got better.
Chances this will be last Moto device? Let's just say this could be my last Moto device, and I have been a big Motorola fan for many years.
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Can anyone link me where to find OTA updates for Moto G5 Plus and, if necessary, instructions? I don't see why the instructions would be any different from the OnePlus 5, other than Motorola making it harder on purpose.
FamilyGuy0395 said:
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Click to expand...
Click to collapse
Never said it was true for every phone or manufacturer, but that is the way it is with Moto devices... You cannot flash an OTA with TWRP, the script checks (among other things) the recovery and will fail if it doesn't have the correct signature, same with the modems, bootloader, partition table, and things in /system. Moto OTA updates are VERY picky and will fail at the drop of a hat on a device that is not purely stock.
The only work around, that works in SOME cases with Moto devices, is using FlashFire by Chainfire, but that is hit and miss, depends on what is updated.
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Karlinski said:
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Click to expand...
Click to collapse
Do you have a link to this thread? I am curious how the modems, partition table, and bootloader updates are handled since TWRP doesn't have the correct signature to write to these partitions. I can see where it could maybe update the boot and system partitions if they were extracted from the ROM, even if they are differential deltas, but my guess is that a "TWRP flashable" OTA is mearly an extract of a blank device's boot and system partition or just he changes, and packed into an OpenRecovery script, and not the "real" OTA file.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Karlinski said:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Q9Nap said:
Do NOT attempt to apply standard OTAs over these builds; they will fail.
Click to expand...
Click to collapse
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
acejavelin said:
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
Click to expand...
Click to collapse
The TWRP flashable stock builds DO upgrade the modem.
As stated in the OP, the only partitions NOT upgraded are gpt and bootloader.
I didn't omit these partitions because they can't be written; I omitted them to prevent potential issues for people who really don't know what they're doing.
Disabling dm-verity is required due to some partitions unavoidably losing their oem signatures during the conversion process.
Disabling force encryption is practically required, as TWRP seems buggy with it enabled.
The intended purpose of these builds is to provide a dead simple (and safe) way for users to return to stock.
I have linked useful tools at the bottom of the OP for those interested in making their own modifications to these stock builds.
Hope this helps :good:
Q9Nap said:
Hope this helps :good:
Click to expand...
Click to collapse
It does actually, thank you... Obviously I have a lot to learn about the differences between current devices and older Moto devices I am used to working.
My F5321 from Malaysia isn't receiving any of the new updates. Last one was 34.4.A.2.32.
Could anyone explain why?
You can check xpericheck.com if there's a newer version,but there's a good chance there isn't one. I'm stuck on 34.4.A.2.50 on the Central Europe version for example, the newest one is .85
Matej101 said:
You can check xpericheck.com if there's a newer version,but there's a good chance there isn't one. I'm stuck on 34.4.A.2.50 on the Central Europe version for example, the newest one is .85
Click to expand...
Click to collapse
Customised MY isn't even listed. :/
What now? Unlocking bootloader if you want latest security patches?
Is there another firmware variant that would be suitable for your location? There may be less difference between the variants than you might expect.
pseudonym58 said:
Is there another firmware variant that would be suitable for your location? There may be less difference between the variants than you might expect.
Click to expand...
Click to collapse
Can you just flash the firmware straight from xperifirm, or do you need an unlocked bootloader or sth?
Bro do not update it to 8.0 oreo is wery bad I swear im back to stock Nougat again
Qendra said:
Bro do not update it to 8.0 oreo is wery bad I swear im back to stock Nougat again
Click to expand...
Click to collapse
true
Matej101 said:
You can check xpericheck.com if there's a newer version,but there's a good chance there isn't one. I'm stuck on 34.4.A.2.50 on the Central Europe version for example, the newest one is .85
Click to expand...
Click to collapse
me too.. central europe and stuck on 34.4.A.2.50, I don't understand why
andy356 said:
My F5321 from Malaysia isn't receiving any of the new updates. Last one was 34.4.A.2.32.
Could anyone explain why?
Click to expand...
Click to collapse
According to xpericheck, singapore region firmware is also stuck in March. I guess both MY and SG are using the sme FW. I think you cn flsh other region FW without unlocking Bootloader.
Is there a way to flash security updates only, without upgrading to oreo?
trewelu said:
According to xpericheck, singapore region firmware is also stuck in March. I guess both MY and SG are using the sme FW. I think you cn flsh other region FW without unlocking Bootloader.
Click to expand...
Click to collapse
Can anyone please confirm this? I'll unlock the bootloader if I have to, but it would be great if it is not needed.
andy356 said:
Can anyone please confirm this? I'll unlock the bootloader if I have to, but it would be great if it is not needed.
Click to expand...
Click to collapse
I'm in USA, and I've flashed f'd from at least 10 different countries and never seen any affect on the phone operation.
andy356 said:
Can anyone please confirm this? I'll unlock the bootloader if I have to, but it would be great if it is not needed.
Click to expand...
Click to collapse
If you want to retain the fingerprint sensor operation, don't flash to US. People here have in the past recommended either DE or UK, as they tend to be updated promptly. No unlocking of bootloader needed.
Okay guys. I'm ready to flash a new firmware, probably Customised UK. Is the guide on xperiablog up to date and accurate? Also, there is a flashtool by Androxyde on flashtool dot net, but there is also a flashtool on Sony Developer World. Which one should I use?
There is only one xperifirm so that's unambiguous, at least.
Edit: also, it doesn't affect user data or the OS in general, does it?
I can only speak from personal experience with the Androxyde flashtool. I've never tried (nor even known about) the Sony flash tool. In my experience, if you don't make any changes to the default settings, the existing user data is carried over into the newly installed firmware. I'm assuming here that you're flashing from one variant of Android 8.0 to another, not from Android 7 to 8, etc.
BTW, I would always advise backing up your data first, of course. If, for some reason, you are dissatisfied with the result, you can normally get a factory installation of your currently-installed firmware by using software restore from SONY (as part of Xperia Companion).
@pseudonym58 Thanks. Is the guide on Xperia blog the one to follow or is there a better one out there?
I don't recall which guide I used. It basically runs like this:
Run Xperiafirm from within flashtool; it will refresh available software. Choose particular phone model and download desired firmware. Back in flashtool proper, connect phone in flash mode. Select downloaded firmware, which is unpacked and prepared for flashing. As I mentioned above, you should not need to make any configuration changes to the default. Flashing can now begin (it might seem to pause temporarily from time to time but don't cancel process).
Don't worry about warnings of missing elements; I have never had a flashing procedure fail as a result of a claimed missing component.
This is just a general procedure; perhaps someone else can recommend the best full tutorial.
Ok so CE1 got the newest (.107) update right now so it can probably be used too.