Hi everyone,
I recently bought a Tencent edition of the ROG Phone 2, and was a bit annoyed to see that automatic system updates no longer worked after converting it to a WW ROM. I did some digging and found out that ASUS uses the IMEI of the device to track what updates the device is entitled to, including the region. So a CN IMEI would only be entitled to CN firmware updates.
That's what led me to write this app that interacts directly with the ASUS servers to look for updates, but using a spoofed IMEI that makes the server think it's WW. It was a bit of work to figure out how it all works, but I have managed it, and it seems to work as it should - I successfully upgraded from .44 to .64 just a short while ago using the app.
Download
v1.0.4:
- Allow input of custom IMEI
- Fix issues on Android 10 beta
- Other fixes
https://github.com/HomerSp/AsusUpdater/releases/download/v1.0.4/AsusUpdater-v1.0.4.apk
v1.0.3:
- Enable downloading updates via mobile data
- Several UI fixes
https://github.com/HomerSp/AsusUpdater/releases/download/v1.0.3/AsusUpdater-v1.0.3.apk
v1.0.2:
- Fix updates not working when on CN fingerprint (for real this time)
https://drive.google.com/open?id=1IgDM9T6u4z4LLLudHYIg3hb6OPw7Qz29
v1.0.1:
- Fix updates not working when on CN fingerprint
https://drive.google.com/open?id=1_hYwPi3Q_8tW6gaBnQvNmohWR4Q4wP2o
v1.0:
- Initial release
https://drive.google.com/file/d/1KVh8OmgMxMg-jQfpF2LmIW4cqBDKXtyz/view?usp=sharing
Instructions
The app is very basic, but it does what it should. It will check for updates every hour, and send you a notification if it has found an update - or you can force a check by opening the app and pressing the button.
Once the update is downloaded (the updater will notify you when it's done), you will need to restart the device, and upon booting again you will be notified by the system that a system update has been found and be asked if you want to apply it or not.
That's really it, the system will handle the updating from there.
Note 1:
You need to be on completely stock firmware for the update to apply properly. The bootloader can be unlocked, but you can't be rooted or such.
Note 2:
For the updater to work correctly you'll have to allow it to auto-start by going to System settings -> Battery -> PowerMaster -> Auto-start manager and make sure ASUS updater is ticked. Not doing this means you will have to run the app once each boot for notification to work correctly.
Note 3:
If the update fails (after rebooting and starting the update), I will need a log to be able to figure out what's wrong. The relevant tag is UpdateLauncher.
Source code:
AsusUpdater - Github
Do let me know if it's working for you, or if you can think of any improvements I can make.
Wow great work mate I will download the app when the next update will be available.
I wish you can develop something for volte and vowifi.
avivv said:
Wow great work mate I will download the app when the next update will be available.
I wish you can develop something for volte and vowifi.
Click to expand...
Click to collapse
+1 for VOWIFI
Sent from my ASUS_I001DE using Tapatalk
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
Hope you can get some more app for our lovely ROG 2 like this. Keep it up...
Sent from my ASUS_I001DE using Tapatalk
This is awesome and quite helpful! I appreciate your time and effort in making this!
HomerSp said:
Hi everyone,
I recently bought a Tencent edition of the ROG Phone 2, and was a bit annoyed to see that automatic system updates no longer worked after converting it to a WW ROM. I did some digging and found out that ASUS uses the IMEI of the device to track what updates the device is entitled to, including the region. So a CN IMEI would only be entitled to CN firmware updates.
That's what led me to write this app that interacts directly with the ASUS servers to look for updates, but using a spoofed IMEI that makes the server think it's WW. It was a bit of work to figure out how it all works, but I have managed it, and it seems to work as it should - I successfully upgraded from .44 to .64 just a short while ago using the app.
Download
https://drive.google.com/file/d/1KVh8OmgMxMg-jQfpF2LmIW4cqBDKXtyz/view?usp=sharing
Instructions
The app is very basic, but it does what it should. It will check for updates every hour, and send you a notification if it has found an update - or you can force a check by opening the app and pressing the button.
Once the update is downloaded (the updater will notify you when it's done), you will need to restart the device, and upon booting again you will be notified by the system that a system update has been found and be asked if you want to apply it or not.
That's really it, the system will handle the updating from there.
Note 1:
You need to be on completely stock firmware for the update to apply properly. The bootloader can be unlocked, but you can't be rooted or such.
Note 2:
For the updater to work correctly you'll have to allow it to auto-start by going to System settings -> Battery -> PowerMaster -> Auto-start manager and make sure ASUS updater is ticked. Not doing this means you will have to run the app once each boot for notification to work correctly.
Do let me know if it's working for you, or if you can think of any improvements I can make.
Click to expand...
Click to collapse
Hats off for you Senior.
I'm on WW_ZS660KL-16.0622.1906.19-0, was never able to update this phone that I imported from China to EU, and your tool doesn't find new updates available to install either. Could it be that I'm on ww firmware but cn fingerprint? (seller's doing, not mine). I'm 100% on stock everything (meaning, I haven't tinkered with the software one bit). Would appreciate some clarification, thank you.
Juraviel said:
I'm on WW_ZS660KL-16.0622.1906.19-0, was never able to update this phone that I imported from China to EU, and your tool doesn't find new updates available to install either. Could it be that I'm on ww firmware but cn fingerprint? (seller's doing, not mine). I'm 100% on stock everything (meaning, I haven't tinkered with the software one bit). Would appreciate some clarification, thank you.
Click to expand...
Click to collapse
As it turns out, the CN fingerprint does affect it; I didn't think it would, but one of the props that the app uses to send to the server actually changes based on the fingerprint.
I've fixed it, so please try this, and let me know if it works:
https://drive.google.com/open?id=1_hYwPi3Q_8tW6gaBnQvNmohWR4Q4wP2o
For me it's the same, unfortunately. Not sure what I could be doing wrong.
Juraviel said:
For me it's the same, unfortunately. Not sure what I could be doing wrong.
Click to expand...
Click to collapse
Sorry, I had completely missed another reference to the CN fingerprint. Try this latest one (tested and working for me with fingerprint changed to CN):
https://drive.google.com/open?id=1IgDM9T6u4z4LLLudHYIg3hb6OPw7Qz29
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Just change the fingerprint to WW, having a WW rom with CN fingerprint will cause more issues.
Juraviel said:
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Click to expand...
Click to collapse
A log would say what's wrong, most likely one of the partitions isn't completely stock - they probably botched something when they flashed the WW ROM on it. Feel free to send me a log and I can have a look.
avivv said:
Just change the fingerprint to WW, having a WW rom with CN fingerprint will cause more issues.
Click to expand...
Click to collapse
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Juraviel said:
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Click to expand...
Click to collapse
Juraviel said:
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Click to expand...
Click to collapse
Sure you can, it's easy just follow this guide, no need to root or to wipe and it takes 5 minutes
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
Juraviel said:
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Click to expand...
Click to collapse
I would indeed recommend changing the fingerprint to WW as having a CN fingerprint causes a whole bunch of issues, although that most likely won't fix your upgrade issue. The EDL method is really easy, and can be done in a couple of minutes - and does not require rooting.
As for the log, have you used adb and such? I just need a logcat. There are plenty of guides on how to do that, so I won't go into that here.
You were right it was fairly easy, although the original tutorial should have a warning that entering in edl mode causes the screen to go black and the phone completely unresponsive! Other than that it went smooth. You did an amazing job.
Edit: well, actually, it still fails I'll keep at it
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
---------- Post added at 10:41 PM ---------- Previous post was at 09:45 PM ----------
kashif31 said:
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
Click to expand...
Click to collapse
Nvm there was an error with the file which was downloaded by your app .. i download the file again n it worked
kashif31 said:
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
---------- Post added at 10:41 PM ---------- Previous post was at 09:45 PM ----------
Nvm there was an error with the file which was downloaded by your app .. i download the file again n it worked
Click to expand...
Click to collapse
If you get this again I would need a logcat to be able to help you. The update dialog you see on reboot isn't from my app, but it's a system app that I have no control over - so there's no way of telling what's causing it to fail, except for a log.
HomerSp said:
If you get this again I would need a logcat to be able to help you. The update dialog you see on reboot isn't from my app, but it's a system app that I have no control over - so there's no way of telling what's causing it to fail, except for a log.
Click to expand...
Click to collapse
How to open logcat
Thanks so much for this app, I was thinking I would just need to apply the updates manually as they came out. It doesn't seem to be downloading the update when I tap the button though, my data usage stays in the KB/s range or lower. Anything I might be doing wrong?
Related
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
condi said:
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
Click to expand...
Click to collapse
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Judah001 said:
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Click to expand...
Click to collapse
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
condi said:
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
Click to expand...
Click to collapse
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Judah001 said:
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Click to expand...
Click to collapse
There was small typo - bad syntax in 1.0, it will make no harm, but will exit when will arrive ota download. Just redownload - v1.1
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
zaynal said:
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
Click to expand...
Click to collapse
Great happy to kick your worries out
Judah001 said:
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
Click to expand...
Click to collapse
So in summary:
everything works correctly,
WiFi issue IS NOT related to multitool.
Im glad
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
obicom said:
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
Click to expand...
Click to collapse
hi friend,
thanks for posting this info - its very important to stay rootable..
about OTA RootKeeper - i've got it installed and got 'protected root'.
Got to check if it works ok in details.
As far as I remember - it worked, but not from the beginning.
I've already reflashed with rootkeeper,
su-backup stays, after reflash you need to reinstall Superuser app.
Will try that when I get back home later evening.
BTW - I think I could get some other, 'extra rootkeeper' for us,
as far as I remember - with some proper permissions we could get
unwritable build.prop - then we could have opportunity to reflash
older 'rootable' zip, if another ota would lock the exploit vulnerability.
I had this one time - reflashed new ota, and build.prop remained untouched
br
condi
My friend,
I guess the magic command should be 'chattri +i'.
This is the way how Root Keeper works.
It should be possible to use the same to protect the build.prop too.
But please consider, to install an older version of update.zip, we need a much lower value in the build.prob. I have two files on my sd card (update.zip) ..
For example .. if my build.prop = 123456789, I got the last version with
123456788 and a older one (e.g. 3.2) with 103456789
Therefore we should increase build.prop for the first step (download latest version) with one and should increase a higher digit for protection as a backup.
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
What do you mean with "I run the bootloop protection"?
Did you reinstall the ota firmware zip via recovery menu?
If yes and if it was successful the boot loop should be gone.
If you try do start boot loop protection script after getting boot loop ...
its to late ... :-(
rfreeman said:
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
Click to expand...
Click to collapse
Code:
pro·tec·tion [pruh-tek-shuhn]
noun
1.
the act of protecting or the state of being protected; preservation from injury or harm.
You get 1000 of viruses, hard disk damaged. And then you buy antivirus software and want pc to work?
You cant protect something, that has already been done.
Now you can FIX, REPAIR, not protect!
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
rfreeman said:
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
Click to expand...
Click to collapse
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
condi said:
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
Click to expand...
Click to collapse
I think your first assessment was correct. It sounds like he already had a bootloop and is now trying to use protection to fix it....
BTW Thanks for the awesome tool. I've had my tablet for about a week but haven't gotten up the nerve to try and root it yet lol =D
These update packages should work on global variant Nokia X6.
Usage:
Confirm your current version by dialing *#*#227#*#* before update.
Then download the package and rename to the specific filename I gave, place it to root directory of internal storage and dial *#*#874#*#* to update.
After the update procedure completed, update package will be deleted from your phone automatically.
Global Release:
Note: From DRG-250A build, it blocked current bootloader unlock method, be careful.
Click to expand...
Click to collapse
June 2018 to August 2018 (DRG-250A-0-00WW-B05-229D-0-00WW-B01-update.zip)
August 2018 to September 2018 (DRG-250B-0-00WW-B01-250A-0-00WW-B05-update.zip)
Android Pie November 2018 (DRG-330B-0-00WW-B01-update.zip)
Thanks for your work supporting our device!
Do you have boot image of 250A version?
izkyline said:
Do you have boot image of 250A version?
Click to expand...
Click to collapse
Yes that would be handy. I read that payload_dumper doesn't work on incremental updates. I'm still looking for ways to extract a boot.img
Hi bro I need to unlock the blltloader for my nonia 6.1 ta-1050 . If you could help me plzz
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
My nokia
DRG-250A-boot_patched.img patched with Magisk v17.1:
https://www111.zippyshare.com/v/12gKJE7u/file.html
how to update the path for x6
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
google play pretent CN OTA?
Boss,
After discuss with many other user, we think it is because I am using China version rom, but installed Google play, which pretent OTA update.
Do you think so? Could you give us a solution?
I bought the phone from ebay. I just need OTA.
yshgcs said:
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
Click to expand...
Click to collapse
Will this work on Android one varient i.e , Nokia 6.1 plus?
Do you have boot image of 250B version? I need root my device, boot September, help me
thaidaidong25 said:
Do you have boot image of 250B version? I need root my device, boot September, help me
Click to expand...
Click to collapse
Use the boot image from Nokia 7 Plus. They work. Just don't flash it, only boot it.
thanks for sharing, i just installed the pie version on my nokia 6.1 plus
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
xoxoJoelxoxo said:
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
Click to expand...
Click to collapse
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
DJBhardwaj said:
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
Click to expand...
Click to collapse
Well, that didn't do the trick, but I just simply clicked 'disable' after wiping the data and it gave me a message of "uninstalling app and installing factory camera app" which worked beautifully.
Now everything's working fine.
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
snowdance said:
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
Click to expand...
Click to collapse
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
hoatongoc said:
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
Click to expand...
Click to collapse
already installed it last night, and it work's !
thank's for the reply
Will I still receive OTA updates by HMD for my device when I check for it?
xoxoJoelxoxo said:
Will I still receive OTA updates by HMD for my device when I check for it?
Click to expand...
Click to collapse
you will, i already ask it with the support center from my country in indonesia
Just received notification on my phone.
Version : A2017GV1.30B02
Size : 1.93GB
1. Updates to Android 8.0
2. Latest security package
Finally.
Greetings from Malaysia.
awesome news! Mine still tells me I'm up to date.
Is there any way to "capture" the update file and share it?
rzarectha said:
awesome news! Mine still tells me I'm up to date.
Is there any way to "capture" the update file and share it?
Click to expand...
Click to collapse
Sorry, but I've got no idea.
Anyway, just downloaded and updated the phone. Very nice clean interface with Launcher3, i.e. default Android launcher. But I use Nova Prime anyway. Everything else in the settings, interface etc is very stock looking.
Security updated to 1 Oct. Remains to be seen whether we'll get up to date security patches.
Will factory reset my phone later and do clean install of my apps, setting up of my phone and will test this thoroughly over the weekend. So far it's looking good.
got it now
Can you post the baseband / modem and kernel version please ?
looks like they updated the security over the US version
and camera probe
Probably no Camera2 api and maybe turn off auto update in dev options to try and capture?
Thanks for posting ??
Checked mine, update showed. Downloading, will try to capture.
RobboW said:
Probably no Camera2 api and maybe turn off auto update in dev options to try and capture?
Thanks for posting ??
Click to expand...
Click to collapse
Well it should be easy to enable it. I remember nfound put a few files from the U version to the G version of the rom during the beta stages. And that enabled working level 3 camera2 api with working gcam. Dunno which files it were and if it still works as good. Some ppl or devs gotta try if it's possible.
Anyway, still disappointed that the zte team for G version didn't implement it. I mean they could have easily used the resources from the US team to get it implemented
Works SuperSu or Magisk with Oreo
"daydream will be unavailable FOR A WHILE" in the change-log screen. Maybe this means that this is not the last update for the Axon 7 and they are looking pushing more updates later.
EDIT: how do we root this thing? The recovery seems to have no fastboot. Do we have an EDL fastboot patch like "FASTBOOT_UNLOCK_EDL_N"?
Actually seems to me there will be some follow up from this OTA later on
It is ZTE though. Words can't always be counted on.
Please do a EDL backup
djkuz said:
Please do a EDL backup
Click to expand...
Click to collapse
You need to reset your phone to factory before you make that public right? otherwise the backup will have all your apps and logins?
I'm happy to reset my phone for you guys and make a backup but I would need to know if there's a way to root this build before I do that.
I have a few apps that I would need to restore from Titanium ASAP after factory reset and if there's no root I'd be in trouble.
rzarectha said:
You need to reset your phone to factory before you make that public right? otherwise the backup will have all your apps and logins?
I'm happy to reset my phone for you guys and make a backup but I would need to know if there's a way to root this build before I do that.
I have a few apps that I would need to restore from Titanium ASAP after factory reset and if there's no root I'd be in trouble.
Click to expand...
Click to collapse
No, not need to factory reset the phone, edl backup not contain userdata or user apps
Alright, thanks for the confirmation. I started a backup. No idea how long does it take. I will upload it on mediafire and post the link here ASAP.
EDIT: just to be sure, you guys need the "backup full edl" option, right?
rzarectha said:
Alright, thanks for the confirmation. I started a backup. No idea how long does it take. I will upload it on mediafire and post the link here ASAP.
EDIT: just to be sure, you guys need the "backup full edl" option, right?
Click to expand...
Click to collapse
Yes, full edl backup!
uploading
https://imgur.com/a/j2pVNu8
---------- Post added at 03:58 PM ---------- Previous post was at 03:31 PM ----------
made a thread for it here for convenience: https://forum.xda-developers.com/axon-7/how-to/a2017gb02oreofulledl-t3861809
I have mine on Oreo now. Some stuff to sort out. SD seems ok so far.
Couldn't find the update file and once you start, you can postpone but not stop it.
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
TESTED IN INDIAN AND BRAZILIAN DEVICES
https://motoota.lolinet.com/index.p...&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE
FOR MEXICAN USERS
https://motoota.lolinet.com/index.p...&carrier=amxmx&sn=SERIAL_NUMBER_NOT_AVAILABLE
Pre-requisites:
1. Battery 50+%
2. Locked bootloader
How to install ?
Step 1: Place the downloaded zip in internal storage and rename it.
( Indian / Brazilian: Blur_Version.29.11.30.albus.retail.en.US.zip or Mexican: Blur_Version.29.11.31.albus.retail.en.US.zip)
Step 2: Go to settings -> apps -> show system apps
and then give storage permission for Motorola update services.
Step 3: Reboot the phone and then check for update in settings app.
#Youtube video tutorial by Rocha Tech
https://youtu.be/xJO31p4GLmU
(Just watch the video without sound if you understand the language )
#FAQ
1. What about my data after i install this update?
Ans: Your data is safe after installing the update. For more safety, you can backup your data as an additional safety measure.
2. Will this work on my bootloader unlocked device ?
Ans: No, it will not work with bootloader unlocked. You need to flash the Oreo stock rom to be able to flash this on your device.
3. Why my country name is not mentioned for updates ?
Ans: You may try Indian update zip file and if it doesn't work then try the Mexican one.
Credits:
Helton Vezzoni @erfanoabdi
Any info about the build, software channel, etc?
XBrav said:
Any info about the build, software channel, etc?
Click to expand...
Click to collapse
Load it up and tell us.
kewlzter said:
Load it up and tell us.
Click to expand...
Click to collapse
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
XBrav said:
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
Click to expand...
Click to collapse
I tried TWRP (installed) didn't work.
I'll try returning to stock and sideloading tomorrow after work.
Ok, trying the stock way:
1) Reboot into bootloader (Power + Vol Down)
2) Select boot into Recovery.
3) At "No Command" Screen, hold down Power and press Vol Up.
4) Load from SD card, or live dangerously like me and sideload via ADB (Minimal ADB and Fastboot seems to work for me)
Will update once the push is complete.
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Up and running here. Didn't like my original image, but after flushing data, it booted fine. It did say I no longer qualify for updates which seems to be a new thing with Motorola and Pie, but common across other devices too. Either way, it all seems to be working.
victorhbm15 said:
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Click to expand...
Click to collapse
Did it work really..??
Do we need unlocked bootloader or will it work for all..
Currently running Stock Oreo Firmware locked Bootloader.
Trying to sideload via ADB, will post results after completion of process.
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
OldUncle said:
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
My smartphone Model name is XT-1710-10, Dual SIM.
I was successfully able to sideload the Update, with the command
"adb sideload Blur_Version.29.11.30.albus.retail.en.US.zip".
It took around 15 to 18 mins for the sideload process to complete, later the phone restarted and showed the usual Moto loading screen for another 12mins or so, for a moment i thought it was stuck, but no, it successfully completed the update process.
Everything is functioning as usual, i noticed that the placement of signal bar, wifi icons, and battery icons on the top right corner of the screen seem to be not proper.
Same is the case with the arrangement of signal and wifi icons on top right portion inside notification drop down menu, seems to be too close to the screen edge.
Additional features I saw after the update are, 3 finger screenshot, Screenshot editor, Media controls provision inside 'Moto Actions'; Attentive display inside 'Moto display'.
Also the addition of "Digital Wellbeing" inside settings Menu.
---------- Post added at 01:33 PM ---------- Previous post was at 01:17 PM ----------
OldUncle said:
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
It took around 3hrs for me to solve the problem, I am still not clear, what was I doing wrong.
What worked for me somehow was... I properly uninstalled the old ADB installations first vis control panel and then downloaded the latest version of adb i.e adb-setup-1.4.6.exe, and repeated the normal procedure of adb sideload, this time it worked.
I couldn't find an option to enable Android Pie navigation gestures, even in System>Gestures, there is no option.
Do existing TWRP and Magisk root work?
Thanks to everyone who replied with advices :good:
It is my first try to Sidload OTA.
I found out that, I needed the latest OPS27.76-12-25-22/23 stock firmware and I was using OPS27.76-12-25-13.
I fastbooted to the latest but, it didn't work again and I think the reason is that my device is XT1710-11 (Chinese), though I have fastbooted it to RETEU version (Modems preserved) and works fine.
If my guess is correct, that means I need to wait for the fastboot version for Pie
snuk182 said:
Do existing TWRP and Magisk root work?
Click to expand...
Click to collapse
its working great
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
saurav112214 said:
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/albus/official/
Get the firmware you need from that link and then fastboot flash it to your device.
But make sure if this OTA Pie is for your device.
XBrav said:
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
Click to expand...
Click to collapse
I too have an XT1710-09 (Europe, RETEU software channel). Any idea if this firmware will work for me? Thanks!