I set a watch on this page to get notified when the Android 11 update appeared, as of a few days ago it's available here - but they weren't kidding about free download being slow, it took me about 5 hours, so I've uploaded the untouched zip to Google Drive in case anyone wants to download it a bit quicker. (I remembered after the fact that I got a tool for downloading from Samsung's servers, then forgot about it)
If you unlocked your phone and rooted with Magisk, don't forget to patch the AP image with the Magisk Manager app first before you flash it (scroll down to "Additional Notes" here about updating, hopefully this is the same guide you used in the first place). If you're still fully stock then you don't need to worry about that, but maybe you can just update officially from your phone. I did the Magisk thing and flashed it with Odin, all went really smoothly, haven't had any errors or glitches and all my stuff is still there.
FWIW this is no longer the latest, there have been two more updates since - the latest ends in BD and is One UI 3.1.
I had a few spontaneous reboots while running the first Android 11 release (the one from the above post), am waiting to see if this newer version avoids them.
Related
Been trying since last night. Whenever I download , it gets stuck in 60% or 93% or smthing like that. When I Pause and Resume it, the download starts all over again. Its over 400mb and I am on limited bandwidth. Must have wasted over 2 GB bandwidth simply trying to get this [email protected] tablet to get updated.
Is there anynfix to this? Can I download it on my PC and transfer to my tablet?
I am using Xolo Tegra Note 7 with Android 4.3... And yes I have more than 1 GB space
Hi,
Google this "tegra-note-4-3-ota-update-won-t-download" and so long as you can find a good
download, you can install OTA update from within android. (I've done it, it works).
Post concerns 4.3 OTA but still relevant to your problem.
Dont think I'm allowed to post links (just joined couple of days ago).
NOTE, 'Updater' mentioned in the post (#20) seems to keep changing its name, to eg 'Nvidia System Update' or just 'System Update' (EDIT: with each new OTA).
Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
GroovyGeek said:
Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
Click to expand...
Click to collapse
Since it's a new version, I downloaded the factory image and flashed everything via fastboot. No problems. In fact, every time I have a problem using flashify or down grading, flashing via fastboot solves everything. Maybe you ought to try doing that.
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
GroovyGeek said:
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
Click to expand...
Click to collapse
I'm sorry to say this, but it's probably down to operator error. Making mistakes is just part of the learning process. Just use the full Google image and be done with it. Don't use OTA with Flashify or TWRP. You could have used flash-all.bat with the -w switch removed to leave your data intact, or used the full image with Flashfire retaining root and TWRP. FF makes life very easy, especially when the security updates come monthly.
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
GroovyGeek said:
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
Click to expand...
Click to collapse
It looks like the Flashify dev has moved on and abandoned his project in Dec. 2015. Flashfire is an awesome product that you should look into. It does have a bit of a learning curve, but well supported by Chainfire. You can still freeload until sometime next year. There is a dedicated thread here on XDA. Works a treat on regular monthly updates, although I prefer to use the full image with FF, rather than OTA. By default it will preserve root and recovery while flashing. Primer and FAQ can be found here. The only good news is you probably won't make that same mistake again!
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.
After half a year of not updating due to the the fact i was rooted, alot of apps started to have small annoying bugs. I also wanted to try out all the new features. I was (and sadly still am) on OxygenOS 5.0.. I decided i wanted to update my device, but since i've had it for such a long time i really didn't want to lose all my data and have to reinstall and relogin to every single app and tweak i've made over the past 6 months. So i looked up on how to accept OTA updates without having to reset, and if possible als not lose root. Now, about 2 days and a lot of work further i still have accomplished nothing.
I'm running windows 10 with all the drivers up to date, a Rooted One Plus 5 running OxygenOS 5.0.1 with TWRP 3.2.1-0 Universal Codeworkx-cheseburger custom recovery.
Here are my problems ;
When sideloading OTA 5.0.1 (to clean up and be able to accept OTA updates again) i get to about 47% and then get the message : Total xfer: 1.00x . I've looked it up and found multiple people with the exact same problem (All posts from 2-3 years ago) but can't seem to find a solution there. I've tried everything (updating drivers, different OxygenOS versions, sideloading via TWRP, wiping and then sideloading) Sideloading with the stock recovery or TWRP still doesn't work.
I now am totally out of options and ask for any of your help. I would be ever so gratefull becasue i really don't want to be stuck on the same OS version for the next couple of years. Thanks in advance!
Luuk
dont worry just copy the file without changing its name to the internal folder of your device. reboot the phone , the notification will appear on the notification panel. This could help some OEM s pl. try
I have completely stock ONN 8 that I've had since launch. It has never received an OTA, and in the past trying to update it with the OTA updates in another thread never worked. For the first time today, the tablet had a notification that there was an OTA update available. The notification says the update has been paused and click resume to continue. When I click "resume" nothing happens and it goes back to paused a few seconds later. I tried factory resetting the tablet and using several different networks, and it will not download the OTA. Any ideas?
just lou said:
I have completely stock ONN 8 that I've had since launch. It has never received an OTA, and in the past trying to update it with the OTA updates in another thread never worked. For the first time today, the tablet had a notification that there was an OTA update available. The notification says the update has been paused and click resume to continue. When I click "resume" nothing happens and it goes back to paused a few seconds later. I tried factory resetting the tablet and using several different networks, and it will not download the OTA. Any ideas?
Click to expand...
Click to collapse
Same behavior for months. Spent time trying to resolve and came to the conclusion the back end mechanism to notify and initiate OTA's is on a different platform (server, url, whatever) than the delivery mechanism. The latter appears to be non-responsive; no one is watching the hen house.
DB126 said:
Same behavior for months. Spent time trying to resolve and came to the conclusion the back end mechanism to notify and initiate OTA's is on a different platform (server, url, whatever) than the delivery mechanism. The latter appears to be non-responsive; no one is watching the hen house.
Click to expand...
Click to collapse
Thanks. My suspicion was that it was server related.
There's like a new update ONA19TB002_20200416.
EDIT Even downloaded and installed. Kind of regret using that Mediatek tool to install 2019111 from the stock/image/ota thread as ever since then the wifi's mac address keeps changing on each boot or wifi is turned off/on.
htcplussony said:
There's like a new update ONA19TB002_20200416.
Click to expand...
Click to collapse
Interesting. Maybe someone will grab the OTA fie and upload it. Unfortunately, it probably won't do me much good, as my tablet doesn't have the November update installed.
I would avoid the update if you can - I came home last night to find mine updated and the screen was mirrored (everything is backwards, including text). A forced reboot didn't do anything. It's basically like looking at it through a mirror as everything is backwards. The odd part is, the touch locations are still in their original locations. So if on the screen, an app is now on the left side (again, backwards), I have to touch the right side of the screen to use it (with the same behavior inside the app - controls all backwards). The update basically made my tablet useless. 100% stock.
no99sqrd said:
I would avoid the update if you can - I came home last night to find mine updated and the screen was mirrored (everything is backwards, including text). A forced reboot didn't do anything. It's basically like looking at it through a mirror as everything is backwards. The odd part is, the touch locations are still in their original locations. So if on the screen, an app is now on the left side (again, backwards), I have to touch the right side of the screen to use it (with the same behavior inside the app - controls all backwards). The update basically made my tablet useless. 100% stock.
Click to expand...
Click to collapse
My update is still "paused". At this point I don't really care. This tablet is so slow it is virtually useless. I doubt an update is gonna make it any better anyways.
My FOTA doesn't even give any updates, just that it's "fully updated." I wonder if I got a test model, as it also came with a multitouch test, had a chinese "factory mode", and had a strange MTK debug mode when I tapped custom build mode.
My unit had an FOTA to the May 2019 but no more updates while on that firmware. The Nov FOTA from the Stock Backups thread wouldn't take and I had to flash the full stock image. It gave me the April 2020 when they released one.
New Update
I know this thread is old, but I received a new update today. It has the July security patch, and the kernel is dated 8/14/2020. It's the first update that actually installed since I got this tablet at launch last year.
Does anybody know how to overcome the problem of getting the latest OTA. I get an error after reboot and trying to flash it, here is the log:
script aborted: unable to use metadata to correct errors
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system image corrupted, attempting to recover...
script aborted: unable to use metadata to correct errors
E1004: system partition fails to recover
E:Error in /sdcard/Android/data/com.adups.fota/files/adupsfota/update.zip (Status 7)
W:failed to read uncrypt status: No such file or directory
25.10 solved the problem by reflashing the stock image from may 2019