Related
I've been willing to change rom for a while now but after digging a little, I haven't found anyone with the same build number of mine.
Also it says my system is the latest version and I cannot update.
imad283 said:
I've been willing to change rom for a while now but after digging a little, I haven't found anyone with the same build number of mine.
Also it says my system is the latest version and I cannot update.
Click to expand...
Click to collapse
it strange that your system doesn't show any update. You should be on 232 now (android 6.0). YOu can try to manually flash the complete rom through sptool or update manually one by one using the inbuilt updater.
Read Here
http://www.techolite.com/35528/lenovo-k4-note-marshmallow-6-0-update-official.html
will this void my warranty?
and thanks a lot for the reply
imad283 said:
I've been willing to change rom for a while now but after digging a little, I haven't found anyone with the same build number of mine.
Also it says my system is the latest version and I cannot update.
Click to expand...
Click to collapse
Your ROM is intended for a specific Telco and more likely you will not receive any update unless your Telco will release the update. If you click system update it will always say it's the latest version. Same case with me here but I already updated to S232. Normally warranty will not be void if you flash using stock ROM. But if you unlock the bootloader the warranty will be void.
atomlife_074 said:
Your ROM is intended for a specific Telco and more likely you will not receive any update unless your Telco will release the update. If you click system update it will always say it's the latest version. Same case with me here but I already updated to S232. Normally warranty will not be void if you flash using stock ROM. But if you unlock the bootloader the warranty will be void.
Click to expand...
Click to collapse
Can you tell me how you updated it yourself, i'd like to do the same for my phone.
Also thanks a lot for the reply <3
I followed the instruction from this post.
[LP][MM] Lenovo K4 Note STOCK Roms (S152) (S232 volte) by anshubham
- Since it was my first time to flash K4 Note, I flashed it with S152 from S102 without unlocking bootloader to preserve the warranty. Of course the FW became generic instead of the original with operator name in it. After I got S152 , I updated it via OTA, a series of updates until I got S232. I hope this helps.
atomlife_074 said:
I followed the instruction from this post.
[LP][MM] Lenovo K4 Note STOCK Roms (S152) (S232 volte) by anshubham
- Since it was my first time to flash K4 Note, I flashed it with S152 from S102 without unlocking bootloader to preserve the warranty. Of course the FW became generic instead of the original with operator name in it. After I got S152 , I updated it via OTA, a series of updates until I got S232. I hope this helps.
Click to expand...
Click to collapse
I Did flashed it to S152 but it seems i've lost my IMEI, how can I get them back? if i update via ota will it be restored? help pls ;-;
Hi all, I'm a US user with W09 and would like to get it to Nougat - I have read the entire "Update to EMUI 5.0" thread and there appeared to be several possible routes, but most were regarding the European version.
I have a US Wi-Fi model and have no allegiance in keeping it a US one, if there's a way to remove the regional aspect to gain access to the update (BETA or otherwise).
I would greatly appreciate if someone who has some experience with or is very confident of the correct path would shed some light for me.
Thank you!
Have you tried update via Firmware Finder? Witch firmware version do you have now?
Sent from my Nexus 6 using Tapatalk
33adi said:
Have you tried update via Firmware Finder? Witch firmware version do you have now?
Click to expand...
Click to collapse
I've just finished reading the entire thread linked above that mentions that method a number of times, so I'm certainly familiar with it, but haven't tried it because sprinkled throughout that thread are plenty of issues encountered. Also, there's no mention of US hardware/firmware specific instructions.
I'm on W09 as mentioned in the OP - thanks for the reply!
Install Firmware Finder from Playstore and post a screenshot with firmwares that appear there.
Sent from my Nexus 6 using Tapatalk
33adi said:
Install Firmware Finder from Playstore and post a screenshot with firmwares that appear there.
Click to expand...
Click to collapse
I'm away from my tablet at the moment but will do later on when I get home.
We will see after that what we can do. I have updated my tablet to Nougat, but I have BTV-DL09 (4G European version).
To change region I think you have to unlock bootloader.
Sent from my Nexus 6 using Tapatalk
33adi said:
We will see after that what we can do. I have updated my tablet to Nougat, but I have BTV-DL09 (4G European version).
To change region I think you have to unlock bootloader.
Click to expand...
Click to collapse
Here's what's in firmware finder @33adi
What's the advantage to switching from US to EU roms? I unlocked, rooted, enabled 5ghz band for wifi, and now only need nougurt but much like the original poster not sure the best route.
Sent from my BTV-W09 using Tapatalk
gaidin43 said:
What's the advantage to switching from US to EU roms? I unlocked, rooted, enabled 5ghz band for wifi, and now only need nougurt but much like the original poster not sure the best route.
Click to expand...
Click to collapse
The advantage of removing the US stock rom is that the European one has a beta available that is very stable. My thread is seeking someone who's confident of the steps to 1st going European & 2nd installing nougat once there, as there was some debate of complexity to doing even that.
I've been through exactly what you are wanting to do @dutchdoggs54 . Unfortunately I can't tell you step by step how I got to where I'm at.
I was on W09128BXXX out of the box . Read the topic that you have linked in your first post and decided to do it using firmware finder to force the update to Nougat as they described. It actually went very well and Nougat worked great with the exception of Bluetooth not working.
I have to say during the upgrade when it booted into recovery and it was TWRP I was concerned. Believe it had an error but it worked and replaced TWRP as I recall with a stock recovery.
So after all that I decided I wanted my tablet branded as a BTV-W09C100B006. Below is the topic where a member thought they bricked their tablet.
https://forum.xda-developers.com/mediapad-m3/how-to/bricked-m3-btv-w09-t3612699
They were given directions to download the Full update package for the version I just mentioned.
This member got their tablet working again and in the process found that 5Ghz wifi is enabled on C100B006 by default.
That was the main reason I rooted my tablet.
I followed the directions knowing I force install a different version of Nougat from your link.
Downloaded the full version software and dropped it in the dload folder on my US tablet and did the upgrade.
Tablet rebooted and shortly after it rebooted again going to recovery (I tried may times to boot). Don't recall the error but after I unlocked my bootloader again it reset the tablet and I was able to access it again. I did relock the bootloader so I can see updates without any problems after that.
In the end I got what I was after. My tablet shows as a BTV-W09C100B006 and can check for updates.
5Ghz wifi is enabled by default. As I said I relocked the bootloader so I'm not rooted. Overall it's works so well I'll wait for Nougat to get released and then do the official upgrade. After the scare of booting to recovery it was worth every nervous minute of it.
Try to talk to OP from this thread:
https://forum.xda-developers.com/p9/...-root-t3374068
Maybe he can make this app available to Mediapad M3, then changing OEMINFO will be easy.
I posted a question there.
No luck
Ok, so I tried following @Samavb's great instructions and guidance in the other thread last night. Made it all the way to the point where he says to install 009 from the Huawei website - got it downloaded and loaded up on the tablet only to find that it wouldn't install because the 009 file on the website is BTV-DL09 not the BTV-W09 version a US tablet would need.
So I got frustrated and tried installing the B301 build that appeared on firmware finder when I was on the W09-006 build...this was nougat and was cool but no keyboard and the play store wouldn't install anything, so I was forced to revert back to 006.
So, long story short, hours of work have confirmed that there doesn't appear to be a way to get a US tablet to fully functional Nougat at the moment. If there was a 009 or 010 build like Samavb mentions for the US model, maybe it would work, but those aren't anywhere to be found - firmware finder, russian site he mentions or otherwise.
So, I'll happily sit on 006 and wait for a US OTA update. That is unless anyone can tell me exactly how to make this US model into a European model.
Same boat as original poster. US w09 on build c128b003. Firmware finder just finds the same version. Anyone know when there might be a us version update released. I thought it was supposed to be may so have been waiting patiently.....but may is over.
dr_pepper said:
Same boat as original poster. US w09 on build c128b003. Firmware finder just finds the same version. Anyone know when there might be a us version update released. I thought it was supposed to be may so have been waiting patiently.....but may is over.
Click to expand...
Click to collapse
In Firmware Finder select the menu in the top left corner. (3 bars)
Right below your model number, select change model and enter BTV-W09C100 and then search.
You should see B301 and it's a full OTA. However, as I understand it this is just a beta/test release.
Only issue I had with it, bluetooth didn't work. Seeing as how I don't use it, didn't bother me.
I highly recommend you fall back to the other topic about forcing the upgrade to Nougat.
Only difference from my tablet and yours. I was on C128B002. I had already rooted and couldn't get that update.
Also US 64gb version here and hoping for an update to Nougat and EM5. Would love to see it!
Huawei have been quite attentive for updates in other markets which is great. Too bad the non-LTE version in US doesn't get the same love.
Buying this tablet was a roll of the dice for me, banking on the hope that Huawei would be attentive to software updates (for all markets) and custom ROMs could serve as back up/enjoyment. This tablet has solid hardware and with another launcher it is decent.
Sadly, my experiment to try out a non-Nexus device without the latest (or close to pure) Android version is coming to an end. The last M3 sold on Swappa went for around $300.
johninsf said:
Also US 64gb version here and hoping for an update to Nougat and EM5. Would love to see it!
Huawei have been quite attentive for updates in other markets which is great. Too bad the non-LTE version in US doesn't get the same love.
Buying this tablet was a roll of the dice for me, banking on the hope that Huawei would be attentive to software updates (for all markets) and custom ROMs could serve as back up/enjoyment. This tablet has solid hardware and with another launcher it is decent.
Sadly, my experiment to try out a non-Nexus device without the latest (or close to pure) Android version is coming to an end. The last M3 sold on Swappa went for around $300.
Click to expand...
Click to collapse
I just updated the firmware finder app and it now shows the full ota for nougat. It wasn't found until I updated the app.
purple lady said:
I just updated the firmware finder app and it now shows the full ota for nougat. It wasn't found until I updated the app.
Click to expand...
Click to collapse
Excellent and great news! Are you in the US and have the wifi only version?
johninsf said:
Excellent and great news! Are you in the US and have the wifi only version?
Click to expand...
Click to collapse
Yep.
Thanks Purple Lady!
Too anyone in this thread, I want to install the latest version available in Firmware Finder.
When I select download, I get 3 file choices. Which should I pick to download then what are the steps to update? Please point me to the best post to reference as there are a few.
johninsf said:
Thanks Purple Lady!
Too anyone in this thread, I want to install the latest version available in Firmware Finder.
When I select download, I get 3 file choices. Which should I pick to download then what are the steps to update? Please point me to the best post to reference as there are a few.
Click to expand...
Click to collapse
from what i gather. if you're going from MM to Nougat, you need to install the Full OTA. for that, there are 2 files, you will need both of them. from there, i'm not sure.
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.
Greetings devs and members:
I have recently begun using a Moto G5 Plus (XT1687 - N. American SKU) that was never updated (due to being in a drawer someplace).
I know that many things have been unlocked and improved by the devs for this particular handset. My question is simply this:
How should I update it? Should I update it?
Should I go OTA (retus) (currently blocking), or should I bypass everything and go directly to Oreo (using the update file, after a factory reset and such)?
Or, hell should I stick with Nougat right now? It seems that lots of folks are having issues, and I just wanted a more informed opinion.
Thank you.
sinister008 said:
Greetings devs and members:
I have recently begun using a Moto G5 Plus (XT1687) that was never updated (due to being in a drawer someplace).
I know that many things have been unlocked and improved by the devs for this particular handset. My question is simply this:
How should I update it? Should I update it?
Should I go OTA (retus) (currently blocking), or should I bypass everything and go directly to Oreo (using the update file, after a factory reset and such)?
Or, hell should I stick with Nougat right now? It seems that lots of folks are having issues, and I just wanted a more informed opinion.
Thank you.
Click to expand...
Click to collapse
To stay with Nougat is not a bad choice, it's a well working system.
If you want to get to Oreo just apply all the OTA updates until you're there. No need to do anything else if your device isn't rooted or the system has been tampered in any other way.
Both firmwares seem to work well.
If the phone is not rooted, then OTA updates are the easiest. Make sure the phone is fully charged or plug it in first. Go to about phone, go to check system updates, accept OTAs until it says up to date, which is likely be Oreo. If it stops at -18 the it may take a few days before the phone alters you to Oreo update.