hi guys
my mia1 was on april patch and rooted.when may update came i uninstalled magisk and unrooted but phone did not update many times with(installation problem )message.
i flashed original mi image 10.4. i.e.january version and wiped phone
but the phone refused to ota update .it only sees may update (385 mb) not 70 mb and download but the same message installation problem.if somebody help me what is wrong and why phone not see feb.,march,april updates and what can be done thanks in advance
Well, you have to try again. Me too passed for that but on the January patch. So I tried once and it works. Here on may update, cheers.
Thaanks for the reply i flashed twrp stock rom april patch and will try till it can update
Related
Hi all,
I updated my phone using the Motorola update manager, but my phone still prompted to download the latest update - I clicked yes, and WIFI only, but it just fails and comes up with an error message and a notification I can't remove. Does anyone know of a way to 'cancel' the update? Or am I stuck with this annoying notification and pop ups?
Thanks for any help
I have the same exact problem...I did the update via sbf... weird..
X3, same problem lol. On wifi it says update not available then says its currently downloading an update but does nothing
Well, then you know exactly what the problem is already.... if you SBF update, you aren't OTA updating, and the phone probably asked you to update OTA and you went ahead and flashed over it. I did that on my phone on Sunday, and had to flash back to 4.1.26 in order to OTA all the way up to 4.1.83, via 4.1.57 first. Follow the steps in order like you should and you won't have any issues - my phone works just fine on 4.1.83 after OTA updating it twice, and rooting it with GingerBreak!
Thanks for the responses guys.
If anyone finds a way of removing this problem without having to flash back and then upgrade again, please share the info!
Cheers.
I've installed gingerblur so the OTA route doesn't work (it gives me this ! mark and did nothing), so I have to use sbf method....I guess I could sbf it to 1.2.6 and then OTA it, but I suspect many of the system changes I made will be gone.
Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.
Hi I have an unrooted 6p I have never messed with the software but I am on the dp program I usually get the updates within hours of it being announced. But for some reason I have not gotten the 7.1.1 stable with December security patch which is odd but anyway I tried side loading the OTA and it gets to 40% and then says installation aborted. I have the and setup right and all that I can reboot into bootloader does anyone know why it would be doing this? When I was at work today I thought maybe if I disable the allow seamless update option in developer options maybe that will allow it. Any thoughts?
Ok I feel like an idiot. I tried again when I got home from work and it seems that the file I am trying to flash is from November 1 which I already have installed. It is the last one one the Google OTA page. So is it not out yet for the 6p? I'm confused can anyone help me out please
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
redduc900 said:
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
Click to expand...
Click to collapse
Ok if I unenrolled from the dp program I should just get the OTA then I won't have to side load is what I'm guessing. It seems that Google had the stable build done before they released the last dp because the file says November 1 build and I got mine on November 5 that is why it won't allow it.
Hey guys, I am facing a weird problem.
I was running the January patch, rooted with magisk, but I was facing some problems so I decided to return to the December Oreo patch.
I flashed the official patch (xiaomi firmware site) and I did a clean flash but after I flashed it when my phone booted it wouldn'1 detect my sim card and it reboots every minute and it's unusable because it keeps rebooting.
I tried flashing the January patch again but the same problem remained and it wasn't fixed.
I tried returning to the Nougat but when I flash the official firmware image, my phone enters a bootloop and doesn't start.
I don't know what caused this problem but I need help.
Update: wifi doesn't work either.
Try to flash the .18 nougat build with miflash, if I remember right it maybe could fix your issue. Nothing to loose anyway and do a clean flash.
Flash persist.img from August build, I'm sure it'll work.
Mazen Amr said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post75251443
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/help/mi-a1-imei-lost-phone-restart-t3735440/page3
I just bought this device, it's on build 1901.339 oreo. I tried updating it to pie via the updater but it didn't show any update. I downloaded latest manual update file(1906.055) and started the manual update process, it started and booted into recovery, after a little progress it said error.
I tried downloading another package(1905.53)to bridge the gap between latest update and my version, same thing happens.
What's the solution guys?
I am very new to Asus, so My build number has 'WW' in it, that means it's SKU is 'WW' right!? and i downloaded the packages with 'WW' in their names.
So i think SKU mismatch isn't a issue here.
Thanks.
sssaini007 said:
I just bought this device, it's on build 1901.339 oreo. I tried updating it to pie via the updater but it didn't show any update. I downloaded latest manual update file(1906.055) and started the manual update process, it started and booted into recovery, after a little progress it said error.
I tried downloading another package(1905.53)to bridge the gap between latest update and my version, same thing happens.
What's the solution guys?
I am very new to Asus, so My build number has 'WW' in it, that means it's SKU is 'WW' right!? and i downloaded the packages with 'WW' in their names.
So i think SKU mismatch isn't a issue here.
Thanks.
Click to expand...
Click to collapse
After 339 you must update to 340 sequentially for OTA updates. V340 is the last Oreo update
Tianhe said:
After 339 you must update to 340 sequentially for OTA updates. V340 is the last Oreo update
Click to expand...
Click to collapse
Thank you it worked