Related
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.
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
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?
If I go into my settings it still says build number Oxygen OS 11.BE86AA and my Android security patch is from 06-01 not updated to 08 yet like in 11.0.1. So I'm guessing if I was on 11.0.1 it would say 11.0.1.BE86AA right? Stupid question I know
JazzieBoi said:
If I go into my settings it still says build number Oxygen OS 11.BE86AA and my Android security patch is from 06-01 not updated to 08 yet like in 11.0.1. So I'm guessing if I was on 11.0.1 it would say 11.0.1.BE86AA right? Stupid question I know
Click to expand...
Click to collapse
Yes currently mine says Oxygen OS 11.0.1.BE89BA.
Did you try manually checking for updates?
Did you try restarting your phone and then manually check for updates?
You can also download the 11.0.1 update here (global version, since your model is BE86AA), and then apply the update locally (Settings > System > System Updates > Settings > Local upgrade). I never did this...
lbsilva said:
Yes currently mine says Oxygen OS 11.0.1.BE89BA.
Did you try manually checking for updates?
Did you try restarting your phone and then manually check for updates?
You can also download the 11.0.1 update here (global version, since your model is BE86AA), and then apply the update locally (Settings > System > System Updates > Settings > Local upgrade). I never did this...
Click to expand...
Click to collapse
Thanks, I'm tryna understand why I can't receive the OTA Safety net check is all good maybe the OS recognizes the modified boot.img
JazzieBoi said:
Thanks, I'm tryna understand why I can't receive the OTA Safety net check is all good maybe the OS recognizes the modified boot.img
Click to expand...
Click to collapse
Once system is modified, you're no longer applicable for updates. You've gotta install them manually.
ninjasinabag said:
Once system is modified, you're no longer applicable for updates. You've gotta install them manually.
Click to expand...
Click to collapse
Yeah I realized this once I flashed my stock boot img back got the OTA lol.
ninjasinabag said:
Once system is modified, you're no longer applicable for updates. You've gotta install them manually.
Click to expand...
Click to collapse
I'm sorry but that's not entirely true. I modified system since I bought this phone and I've been notified about every single update (just gotta do the update as mentioned on the root thread in order to avoid bricking your device).
I even got the Android 11 update.
lbsilva said:
I'm sorry but that's not entirely true. I modified system since I bought this phone and I've been notified about every single update (just gotta do the update as mentioned on the root thread in order to avoid bricking your device).
I even got the Android 11 update.
Click to expand...
Click to collapse
Meant this more for the people who installed the global oem rom.
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
This also what happened to me.
szophiya said:
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
JazzieBoi said:
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
Click to expand...
Click to collapse
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
arda99 said:
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
Click to expand...
Click to collapse
Wow I had no idea metro did that. I knew metro doesn't like unlocked bootloader's and are strict. I will never buy one in my life .
szophiya said:
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Click to expand...
Click to collapse
You could try flashing the stock boot.img via fastboot to see if it finishes installing. https://forum.xda-developers.com/attachments/boot-11-0-1-be88cf-img-zip.5399231/
You'll need to reboot to fastboot and then run: fastboot flash boot_a boot-11-0-1-be88cf-img and then fastboot boot_b (img filename). Try rebooting and performing the update then.
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Misclicked and did a double post, sorry.
szophiya said:
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Click to expand...
Click to collapse
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
JazzieBoi said:
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
Click to expand...
Click to collapse
The MSM you provided is for BE86AA and BE89BA, not for BE88CF which is what they need.
As far as I know, no MSM exists for BE88CF: https://forum.xda-developers.com/t/...8cf-11-0-2-be88cf-rooting-impossible.4367271/