Database Users

Download Unsuccessful

I am getting this goofy "Download Unsuccessful" message in my notifications tray every hour or so. I know I am not intentionally downloading anything. It drives me nuts though. Has anyone else seen this or figured out how to make it stop if you have?
Phone is rooted and I am running MoDaCo 1.1
Thank in advanced.
On a personal note, everytime I come to ask a question I get carried away on other posts and always forget to post my own questions! LOL!

I would guess it's one of two things-
There is an app in the market that is trying to download but is failing.
or
It's trying to push the 1.56 update to you but it's failing (or did you apply it already?)

Flipz, I need you in the office next to mine so I can constantly ask questions.
Well, I am running MoDaCo 1.1, which I don't think has the update packaged with it, but! I checked for Firmware updates and nothing is available.
Now as far as something downloading from the market, would it continue to retry or something if it failed?? Seems like everything I have wanted to download has worked and is installed.
Would there be a way to "Clear the queue?" if there was something that keeps trying???

you can go to marketplace/my downloads. if anything is pending it should let you know there.
otherwise i would guess its in the browser. browser/menu/more/downloads
this happened to me yesterday... well not exactly this but i started downloading an app from the market then did a nandroid restore real quick and as soon as it booted everything was messed up after that.

thedudejdog said:
you can go to marketplace/my downloads. if anything is pending it should let you know there.
otherwise i would guess its in the browser. browser/menu/more/downloads
Click to expand...
Click to collapse
Market place has everything listed as installed or update available.
Browser download history is empty.
Just remembered I had Dolphin Browser installed, there was a download from 11/26 in there that had failed. I think I tried to download an exe without Crutch. We'll see if it was continuing to try and get this file.

Well guys, again thanks for the help. It seems that Dolphon Browser had a failed download being held hostage. Manually going in and clearing it out looks like it has been stoped. Wonder why it doesn't do this on its own after it warns you of its failure. Maybe I'll try and figure out who writes Dolphin and ask them.

Lost 1.141 Update

Hey folks,
maybe someone can help me.
In the morning on my A500 appeared an update available message. I tried to install it, but it failed in the middle. So I got a brick, which I solved with the chinese update. Afterwards I pushed my saved system.img.
BUT: Now the Build Number says Acer_A500_1.112. instead of Acer_A500_1.112.01_EMEA_CUS7
I checked the build.prop but there the correct build number is written.
Also another check of update gimme the message, that my system is up-to-date.
Is anyone able to provide help, like EMEA flexrom.img, boot.img, or some useful advises?

There is a EMEA signed update.zip floating around. Try to restore with that one and see what happens.

I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?

gotta push flexrom
You gotta push your flexrom image onto the tablet too then "FACTORY RESET". The flexrom (mmcblk0p6) has the information of the update... that is where you are getting the difference from (if i am not mistaken)...
Try that and see if it helps ... I believe it should... jejeje

xo96 said:
I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?
Click to expand...
Click to collapse
Nope, mine was rooted with gingerbreak 1.20 and worked fine.
did you delete/rename any phone apks???
or delete/rename any stock software???
I have not messed or removed anything, was rooted, root-explorer/titanium loaded and updated without issue.
reran gingerbreak afterwords and all is well....

Have never seen any OTA update in Australia :|

Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)

ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje

threedfreek said:
Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)
Click to expand...
Click to collapse
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.

Another thing that can cause the update to hang would be any edits to your build.prop (ie. Netflix early fixes, etc). Changing back to the original resolved the triangular fail icon for me and completed the update with root still installed, gingerbreak did have to be I installed again but root is still attainable.
Sent from my A500 using XDA Premium App

Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.

fcmugen said:
Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.
Click to expand...
Click to collapse
You are correct, there is a thread in the general fourm with a link to all the apk's that came stock on the system.
I can't post links yet, but either thread about the OTA update you will find your required apk's.

mapaz04 said:
ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje
Click to expand...
Click to collapse
Full charge, 3 hours... phone 40pct... overall so far more laggy.. nice update

daveid said:
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.
Click to expand...
Click to collapse
Alright... how long has that been there? THANKS!!!

I have the /system/app folder uploaded if u need it... Here is the link...
http://forum.ppcgeeks.com/acer-iconia-a500/143826-system-app-recovery-acer-a500-iconia-tablet.html
Sent from my T7575 using Board Express

Reset back to stock and still cant update.
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?

Where u @ gravy? Some people still haven't gotten the update yet. I didn't get it this morning when I tried but am hoping I get it tonite when I get home... jejeje
PS... I'm in tennessee
Sent from my T7575 using Board Express

I was having all kinds of problems not getting the update to run and kept Triangle halt..
I resolved it by the following:
you dont need to do anything with Gingerbreak, its ok. The problem is for those that changed any system files. In my case, i wanted exchange, so i was using a different email.apk, well as learned from another thread here, if you look in Cache/recovery/logs, you will see a file where you can see where the update went wrong. Like i said, in my case, i saw the file size was not what was expected for email.apk. I removed the exchange account, used rootexp and renamed email.apk.old (the original) to email.apk and the obex file then the update worked correctly.
I was going crazy as i was messing with this instead of watching my heat vs the bulls 1st half.

gravyplaya said:
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?
Click to expand...
Click to collapse
look at your /Cache/recovery/logs for an error and post results

I had to try about 7-8 times looking in the recovery log after each time to see what .apk that i forgot that I had deleted, then put it back and try again. I finally was successful and haven't seen much difference other than no random wake ups. Maybe a little snappier.
I had mine hang in recovery every unsuccessful update which is NOT THE SAME AS BRICKING.

Kill the kill switch - "ST - yy"

< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive

Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.

"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!

Just as I suspected!!

Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.

tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)

tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?

bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks

Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!

So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?

Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.

fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings

Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home

fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.

Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?

fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.

Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!

Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?

bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore

Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!

Android 10 Verizon Variant update!

I had to manually check, but it's here on my phone .

For some reason the screenshot wouldn't upload, so here it is on imgur.
http://imgur.com/a/09FTqvK

Yep. Here in the Seattle area, the Verizon Android 10 update is here for the Moto Z4. Update went without a hitch...phone runs well and smoothly.

Anyone know how to get rid of this? It just started after the updated lol.

I think they put that there to remind us that once Android 11 is released, we'll be stuck on Android 10.

jwhistler said:
I think they put that there to remind us that once Android 11 is released, we'll be stuck on Android 10.
Click to expand...
Click to collapse
?. Trolled by Moto lol

slaytanic said:
Anyone know how to get rid of this? It just started after the updated lol.
Click to expand...
Click to collapse
It's there because developer tools are enabled, if you turn them off that message disappears.

I had the update last week, but was waiting for it to come up on Software update center since I have retail version, but now update is gone and it hasn't been released on the update center.

Could someone pull the update and post it here for the rest of us to manually update??

There is a new one today, it said critical, and applied itself, no option to delay it, it's called Update 5+.

I agree we really need the system image for this update. My phone will not update using the update system option, it only tells me it's already up to date. I tried using the tool from Verizon, same thing, up to date. I called verizon, after the second tech they want to send a new phone. But I don't really want a new phone. Also they had me do a factory reset just to be sure. I had a lot of apps disabled, and had other modifications through adb. Turns out those weren't the issue.
Pretty Please with Sugar on Top.

I'm sure all it would take is for someone to use the Verizon update tool or whatever it's called and select reinstall but keep my days then it'll download and extract. You just have to grab it once it starts extracting the zip and copy it somewhere so that when it finishs extracting it doesn't get removed. The app deletes the system image/zip when it finishes extracting. You could also unplug your phone when it starts extracting and it would touch your device.
Edit...... Then upload it anywhere.

This is an excellent idea, however it'll only work for people already on 10. Myself and others cannot update neither OTA or using the update tool. Using this aforementioned method of extraction would be absolutely fabulous, and I myself would buy some beers for anyone that would pull the update whatever way they can and upload???

Just manually checked and the update was there. I didn't think of it but there used to be an app that a Dev put out for Moto phones that would copy the update. Probably to old to work anymore though.

I did the same thing a couple days ago.

It's finally in the repository

shane1 said:
Just manually checked and the update was there. I didn't think of it but there used to be an app that a Dev put out for Moto phones that would copy the update. Probably to old to work anymore though.
Click to expand...
Click to collapse
Ive used LMSA (lenovo motorola smart assistant). Just set the download folder to someplace you recognize, then copy it out of that folder before lmsa extracts the zip

There is a new update, QDFS30.130-42-1-2, or System Update 6, installing now
Edit: It's May 1st security patch

moxtrom said:
There is a new update, QDFS30.130-42-1-2, or System Update 6, installing now
Edit: It's May 1st security patch
Click to expand...
Click to collapse
Be careful that build of Android 10 has problems with blue tooth according to forums.motorola.com.

pan815kev said:
Be careful that build of Android 10 has problems with blue tooth according to forums.motorola.com.
Click to expand...
Click to collapse
%#*%^$^%$#$(&!! I've been scouring the web all evening trying to figure out why my bluetooth stopped functioning recently...all worked fine until this new update that came across on my phone yesterday. I haven't been able to find any info on this, I was starting to think I was the only one having issues after that update. Is there a fix for this?

Just updated to OS 11; Cannot Download OS 11.0.2.2.1N11AA Update; How to Do?

I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.

reilus said:
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
Click to expand...
Click to collapse
Hello again
So are you rooted at the moment? Do you have oxygen updater installed?
If you are rooted then please disable any and all active modules then reboot your phone.
Then open oxygen updater.
Accept the agreement and provide it any rights it needs then take the update (a full update)
It'll push it to your phone.
Go to settings /system updates / local upgrade.
Choose the zip downloaded by oxygen updater.
Do not reboot when it's complete.
Press home then reopen magisk and click install, then click install to inactive slot after OTA.
Let they install then click reboot, that should be it.
If you're not rooted then let me know.
PS: that's my thread btw, your rationale doesn't quite make sense, an answer could have been given and thanks provided or not. Meaning their name doesn't necessarily have to come up again at all.
It's not that long a thread tbh. The amount of responses I've had and issues addressed and resolved I would say that pretty much any issue to do with payload dumper, root has been addressed

Thank you! I was just about to say, I ended up using Oxygen updater and then doing a local install.
I cannot do an incremental update, but I can do a full update.
I did have an interesting problem, which I also solved. I could not do the OTA install of Magisk! So, I swiped the Oxygen Updater off the recents. Then I tried again and it worked! So, if anyone else has that issue, maybe that will help them !
And I understand that my rationale is flawed, any rational position is flawed. In fact, you won't find any epistemic approach -- even science -- without flaws. I declared my biases and methods to show that I feel I put in a reasonable effort before asking for help. I hope that was part of your understanding. =)

reilus said:
Thank you! I was just about to say, I ended up using Oxygen updater and then doing a local install.
I cannot do an incremental update, but I can do a full update.
I did have an interesting problem, which I also solved. I could not do the OTA install of Magisk! So, I swiped the Oxygen Updater off the recents. Then I tried again and it worked! So, if anyone else has that issue, maybe that will help them !
And I understand that my rationale is flawed, any rational position is flawed. In fact, you won't find any epistemic approach -- even science -- without flaws. I declared my biases and methods to show that I feel I put in a reasonable effort before asking for help. I hope that was part of your understanding. =)
Click to expand...
Click to collapse
If you are rooted then you're certainly not meant to do an incremental OTA as it needs to be a full update.
Haha and no need to prove your efforts to me pal, it's all good.
Just glad you're sorted.
PS: I've actually just updated the thread as 11.0.3.3 just arrived.
I've provided a patched boot img and have updated the guide already

reilus said:
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
Click to expand...
Click to collapse
I always have the same problem when I try to update. For whatever reason before I update I have to flash boot the "stock" boot.img and then my phone will accept the update.

State.of.mind said:
I always have the same problem when I try to update. For whatever reason before I update I have to flash boot the "stock" boot.img and then my phone will accept the update.
Click to expand...
Click to collapse
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA

dladz said:
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
Click to expand...
Click to collapse
dladz said:
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
Click to expand...
Click to collapse
I was sharing my experience with updates. Regardless of the update platform Oxygen Updater or One Plus I ALWAYS have to flash the stock boot.img prior to receiving an update.
I think the problem could be that when I flash the patched magisk boot image I flash it to both slots and not one single slot. I'll try the newer method when another update is released.

State.of.mind said:
I was sharing my experience with updates. Regardless of the update platform Oxygen Updater or One Plus I ALWAYS have to flash the stock boot.img prior to receiving an update.
I think the problem could be that when I flash the patched magisk boot image I flash it to both slots and not one single slot. I'll try the newer method when another update is released.
Click to expand...
Click to collapse
Yep again mate you don't need to do that, regardless where you download the update from provided it is in fact a full update